What problem does it solve?
It prevents false “done/passing” claims by requiring fresh, evidence-based verification before you express completion.
Core Features & Use Cases
- Evidence-first completion: Forces the sequence “run → inspect evidence → only then claim success,” reducing dishonest or accidental overstating of status.
- Verification tiers for common stacks: Uses
verify:full for implementer/QA workflows and verify:quick for reviewers, aligning effort with role.
- Robust fallback when project scripts are missing: Still requires running the underlying lint/typecheck/test/build commands rather than relying on prior runs.
- Use Case: Before merging or finishing a task, verify that linting, typechecking, tests, and (when applicable) build/coverage truly pass, then include the confirmation evidence in your final status.
Quick Start
Use this skill when you are about to report the work is complete: run the appropriate verification tier command for your project, confirm the success gate output, and only then state the result with the evidence line.