What problem does it solve? AI agents and developers often claim work is done, tests pass, or bugs are fixed without actually running the verification commands, leading to broken builds, shipped defects, and lost trust. This Skill enforces an evidence-first discipline so no success claim is made without fresh command output. ## Core Features & Use Cases - Verification Gate: A five-step gate (identify, run, read, verify, claim) that must be completed before any completion statement. - Claim-to-Evidence Mapping: A table mapping common claims (tests pass, linter clean, build succeeds, bug fixed) to the exact command output required to support them. - Rationalization Blocking: Explicit counterarguments for common excuses like "should work", "just this once", or "the agent reported success". - Use Case: Before committing a bug fix, run the test suite, confirm zero failures in the output, verify the regression test fails without the fix, and only then report completion with the evidence attached. ## Quick Start Ask the agent to verify the fix by running the full test suite and only claim completion after confirming the output shows zero failures.
