Verification Before Completion sets one rule: no completion claims without fresh verification evidence. Before saying anything is done, the agent identifies the command that proves the claim, runs it in full, reads the output and exit code, and only then states the result with the evidence.
What You Get
- A five-step gate: identify, run, read, verify, then claim
- A table of claims, the evidence each needs and what falls short
- A red-flag list of wording that implies success without a run
- Patterns for tests, regression tests, builds, requirements and delegated work
Common Use Cases
- Before committing or opening a pull request
- After a subagent reports success
- Before marking a plan task complete
What Makes It Unique
It covers wording as well as behavior: paraphrases, synonyms and expressions of satisfaction all count as claims that need evidence. It also includes a red-green check for regression tests, requiring the test to fail with the fix reverted.
Under The Hood
Instructions only. The skill ships no scripts and calls nothing itself. It sends the agent to run whatever verification command fits the claim, such as a test runner, linter or build, and to check the version control diff after delegated work.