How do I know if the verification was successful?

The QA agent will provide a structured response of VERIFIED, NOT VERIFIED, or PARTIAL, along with specific error details and suggestions if the fix failed.

Does this skill work with any testing framework?

Yes, it is framework-agnostic. It can execute any command-line instruction, including pnpm, npm, Vitest, Jest, and tsc (TypeScript Compiler).

What is the primary benefit of using the verify-fix skill?

The primary benefit is context management. It allows Claude to verify work using a subagent, meaning huge build or test logs won't take up space in your main conversation window.

Can I use this for non-testing tasks like builds or scripts?

Absolutely. It is designed to verify any command-line action, such as checking if a new build script works or confirming that a package generates the correct dist files.

QA Fix Verifier

Name: QA Fix Verifier
Author: hejhi

byhejhi

Security & Testing

Delegates code fix and change verification to a specialized QA subagent to maintain a clean development context.

About

The verify-fix skill optimizes the AI development workflow by offloading the validation of bug fixes, script updates, and type changes to a dedicated QA subagent. Instead of cluttering the primary conversation with lengthy build logs or test outputs, this skill enables a structured delegation process where a verifier agent executes commands, analyzes results, and reports back a clear success or failure status. This ensures that every fix is end-to-end verified without sacrificing the context window's efficiency.

Key Features

Subagent delegation for off-context verification
Structured success reporting (Verified/Not Verified/Partial)
Support for custom verification scripts and commands
0 GitHub stars
Automated TypeScript type-check and build validation
Context preservation by hiding verbose terminal outputs

Use Cases

Confirming a bug fix resolves an issue without polluting the main chat context with logs
Validating new package.json scripts or CI commands in a controlled environment
Verifying complex TypeScript type changes across a monorepo structure

About

Key Features

Subagent delegation for off-context verification
Structured success reporting (Verified/Not Verified/Partial)
Support for custom verification scripts and commands
0 GitHub stars
Automated TypeScript type-check and build validation
Context preservation by hiding verbose terminal outputs

Use Cases

Confirming a bug fix resolves an issue without polluting the main chat context with logs
Validating new package.json scripts or CI commands in a controlled environment
Verifying complex TypeScript type changes across a monorepo structure