skills.rest
MoofonLi
MoofonLiCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

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

2|Updated Jul 11, 2026
Search Tags:#code quality#testing#tdd#verification#evidence#ci#completion claims
One-click install
npx skills add https://github.com/MoofonLi/dev-ready --skill verification-before-completion-moofonli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/MoofonLi/dev-ready/tree/main/src/dev_ready/templates/claude/skills/verification-before-completion
Command: npx skills add https://github.com/MoofonLi/dev-ready --skill verification-before-completion-moofonli

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 commits and false status reports. This Skill enforces an evidence-before-claims discipline so no completion statement 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 claim, commit, or PR. - Failure Pattern Catalog: Maps common claims (tests pass, linter clean, build succeeds, bug fixed) to the exact evidence required and what does not count as proof. - Rationalization Prevention: Lists excuses like "should work now" or "agent said success" and counters each with the required verification action. - Use Case: Before committing a bug fix, the agent runs the test suite, confirms zero failures in the output, verifies the regression test fails without the fix, and only then reports the bug as fixed with evidence. ## Quick Start Ask the agent to verify the fix with fresh test output before claiming the task is complete or creating a pull request.

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 tests pass before committing code?▼

Run the full test command fresh in the current session, read the complete output, and confirm zero failures and a successful exit code. Only then state that tests pass, citing the actual output as evidence.

What counts as proof that a bug is fixed?▼

Proof requires running a test that reproduces the original symptom and seeing it pass after the fix. For regression tests, verify the red-green cycle: the test must fail without the fix and pass with it.

Does a passing linter mean the build succeeds?▼

No, a linter passing does not prove compilation or build success. You must run the actual build command and confirm it exits with code 0 before claiming the build passes.

Can I trust a subagent's success report without checking?▼

No, agent success reports are not evidence. Independently verify by inspecting the VCS diff, confirming the expected changes exist, and running relevant verification commands yourself.

When should verification run in a development workflow?▼

Run verification before any completion claim, expression of satisfaction, commit, pull request, task handoff, or move to the next task. Partial checks and previous runs do not count as current evidence.

Related Skills

Explore More Software Engineering Skills→
U1traVenoU1traVeno

implement

Implement work from a spec or tickets using TDD, typechecking, and code review.

Community
Intermediate
j0rugej0ruge

cy-final-verify

Enforces fresh verification evidence before completion claims, commits, and pull requests.

Community
Intermediate
thisismynewfmail-uithisismynewfmail-ui

requesting-code-review

Verifies code changes before commit via diff analysis, tests, and linters.

Community
Advanced
AndreaCadonnaAndreaCadonna

cicd-pipeline

Design GitHub Actions CI/CD pipelines for Node.js/TypeScript projects with quality gates and staged deployments.

Community
Advanced