skills.rest
erwinv2k-TKG
erwinv2k-TKGCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Enforces running verification commands before claiming work is complete or passing.

Updated Mar 26, 2026
Search Tags:#code quality#testing#tdd#verification#evidence#build validation#completion claims
One-click install
npx skills add https://github.com/erwinv2k-TKG/AgentesVSC --skill verification-before-completion-erwinv2k-tkg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/erwinv2k-TKG/AgentesVSC/tree/main/packs/superpowers/skills/verification-before-completion
Command: npx skills add https://github.com/erwinv2k-TKG/AgentesVSC --skill verification-before-completion-erwinv2k-tkg

SYSTEM DOCUMENTATION & REQUIREMENTS

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 builds, shipped defects, and lost trust. This Skill enforces an evidence-first discipline so no completion claim is made without fresh command output. ## Core Features & Use Cases - Verification Gate: Defines a five-step gate (identify, run, read, verify, claim) that must be completed before any success statement. - Failure Pattern Catalog: Maps common claims (tests pass, build succeeds, bug fixed) to the exact evidence required and what does not count as proof. - Rationalization Blocking: Lists red-flag phrases and excuses like "should work" or "agent said success" and counters each with the required verification action. - Use Case: Before committing a bug fix, run the test suite, confirm zero failures in the output, and only then state the fix is verified with the evidence attached. ## Quick Start Ask the agent to verify the fix by running the full test suite and reporting the actual output before claiming the task is complete.

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 the claim, run it fresh and in full, read the complete output including exit code, and only then state the result with that evidence. Never commit based on previous runs or assumptions.

What counts as proof that tests pass?▼

Only the actual test command output showing zero failures counts as proof. A previous successful run, partial checks, or confidence that the code should pass are not sufficient evidence.

Can I trust an agent's success report without checking?▼

No. Agent success reports must be independently verified by inspecting the version control diff and confirming the changes actually exist and work before reporting completion.

Why is linter output not enough to claim a build succeeds?▼

Linters check style and static issues but do not compile or build the code. A build claim requires running the actual build command and confirming exit code 0.

How do I verify a regression test actually works?▼

Use the red-green cycle: write the test, run it to confirm it passes with the fix, revert the fix and confirm the test fails, then restore the fix and confirm it passes again.

Related Skills

Explore More Software Engineering Skills→
nobelknobelk

tdd-bugfix

Reproduce bugs with failing tests and verify fixes via the full test suite.

Community
Advanced
p-o-ke-naep-o-ke-nae

github-flow

Guide GitHub Flow branching, commits, testing, pull requests, and squash merges.

Community
Intermediate
Devsoul2026Devsoul2026
150

requesting-code-review

Automate pre-commit verification with static analysis, tests, and lint checks.

Community
Advanced
babywormbabyworm
43

rtl-block-contract-test-policy

Automate contract testing and merge-time verification for block-parallel RTL development.

Community
Advanced