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 code, lost trust, and wasted rework. This Skill enforces an evidence-first discipline so no completion 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 success statement, commit, or PR. - Claim-to-Evidence Mapping: A table mapping common claims (tests pass, build succeeds, bug fixed) to the exact command output required to support them. - Rationalization Detection: Red-flag phrases and excuse patterns ("should work", "just this once", "linter passed") that signal unverified claims. - 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 Before claiming any task is complete, run the relevant verification command, read the full output, and only then state the result with the evidence.