verification-before-completion

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

Updated Dec 19, 2024
One-click install
npx skills add https://github.com/DNepovim/yadm --skill verification-before-completion-dnepovim
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/DNepovim/yadm/tree/main/.claude/plugins/cache/claude-plugins-official/superpowers/5.0.6/skills/verification-before-completion
Command: npx skills add https://github.com/DNepovim/yadm --skill verification-before-completion-dnepovim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents and developers often claim work is complete, 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 mandatory five-step gate (identify, run, read, verify, claim) that must be completed before any completion statement. - Failure Pattern Catalog: Tables mapping common claims (tests pass, build succeeds, bug fixed) to the exact evidence required and what does not count as proof. - Rationalization Blocking: Explicit counterarguments for excuses like "should work", "linter passed", or "agent said success". - Use Case: Before committing a bug fix, the agent runs the full test suite, confirms zero failures in the output, and only then reports the fix as verified with the evidence attached. ## Quick Start Before claiming any task is done, run the relevant verification command, read the full output, and only then state the result with the 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?▼

Identify the command that proves your claim, run it fresh and in full, read the complete output including exit code, and confirm it matches your claim. Only then state the result, citing the evidence such as test counts or exit status.

What counts as evidence that tests pass?▼

Evidence is the actual output of a freshly run test command showing zero failures. Previous runs, partial checks, or statements like "should pass" do not qualify as verification evidence.

Does a passing linter mean the build succeeds?▼

No, a linter does not check compilation. Build success requires running the actual build command and confirming it exits with code 0, since linting and compilation are separate verification steps.

How do I verify a regression test actually works?▼

Use the red-green cycle: write the test, 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 an agent's success report without checking?▼

No, agent success reports must be independently verified. Check the version control diff to confirm the claimed changes actually exist before reporting the task state to others.