verification-before-completion

What problem does it solve? AI agents and developers often claim work is done, bugs are fixed, or tests pass without actually running the verification commands, leading to false success reports and broken commits. This Skill enforces an evidence-first discipline so every completion claim is backed by fresh command output. ## Core Features & Use Cases - Evidence Gate: Requires identifying, running, and reading the full output of a verification command before any success claim is made. - Failure Pattern Catalog: Maps common claims (tests pass, build succeeds, bug fixed, requirements met) to the exact evidence required and what does not qualify. - Rationalization Blockers: Lists common excuses ("it should work", "the linter passed", "the agent reported success") and the correct evidence-based response. - Use Case: Before committing code or creating a PR, the agent re-runs the full test suite, confirms zero failures in the output, and only then reports completion with the evidence attached. ## Quick Start Before claiming any task is complete, run the relevant verification command and report the actual output as evidence.