verification-before-completion

Enforces running verification commands and reading output before claiming work is complete.

10|3|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Cynthia1070711/PHYCOOL_Tools --skill verification-before-completion-cynthia1070711
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/Cynthia1070711/PHYCOOL_Tools/tree/main/config-templates/claude/skills/verification-before-completion
Command: npx skills add https://github.com/Cynthia1070711/PHYCOOL_Tools --skill verification-before-completion-cynthia1070711

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents and developers often claim work is done, fixed, or passing without actually running tests or builds, leading to broken commits, false status reports, and lost trust. This Skill imposes a strict evidence-before-claims gate so no completion statement is made without fresh verification output. ## Core Features & Use Cases - Five-Step Gate Function: Identify the proving command, run it fresh, read full output and exit codes, verify the result matches the claim, then state the claim with evidence. - Failure Pattern Catalog: Maps common claims (tests pass, build succeeds, bug fixed, agent completed) to the exact evidence required, plus red-flag phrases like "should work" or "probably fixed" that must stop execution. - Rationalization Prevention: Counters excuses such as "just this once", "linter passed", or "agent said success" with explicit reality checks, including TDD red-green regression verification. - Use Case: Before committing a bug fix or creating a PR, the Skill forces you to run the full test suite, confirm zero failures in the output, and only then report completion with the evidence attached. ## Quick Start Before marking this task done or creating a PR, apply the verification-before-completion gate: run the full test command, read the output, and report the result with evidence.

Frequently Asked Questions about verification-before-completion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify work is complete before committing code?

Run the full verification command for your claim, such as the test suite or build, then read the complete output and exit code. Only state the claim after the output confirms it, citing the evidence like "34/34 tests pass".

What counts as evidence that tests pass or a bug is fixed?

Evidence is fresh output from the actual verification command showing zero failures or exit code 0. Previous runs, linter results, partial checks, or assumptions like "should pass" do not qualify as evidence.

How do I verify a regression test actually works?

Use the red-green cycle: write the test and run it to confirm it passes, revert the fix and confirm the test fails, then restore the fix and confirm it passes again. A test that only passes once is not verified.

Can I trust a sub-agent's success report without checking?

No. Agent success reports must be independently verified by inspecting the VCS diff and confirming the actual changes exist. Trusting an agent's report without verification is listed as a common failure mode.

When should the verification gate be applied?

Apply it before any success or completion claim, expression of satisfaction, commit, PR creation, task handoff, or delegation to agents. The rule covers exact phrases, paraphrases, and any implication that work is correct or done.