skills.rest
D1ssolve
D1ssolveCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

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

1|Updated Jun 1, 2026
Search Tags:#code quality#testing#validation#verification#test-driven development#evidence#completion claims
One-click install
npx skills add https://github.com/D1ssolve/craft-agents --skill verification-before-completion-d1ssolve
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/D1ssolve/craft-agents/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/D1ssolve/craft-agents --skill verification-before-completion-d1ssolve

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 false success reports and broken commits. 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 Prevention: Lists excuses like "should work now" or "linter passed" 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, verify the regression test fails without the fix, and only then report completion with evidence. ## Quick Start Before claiming any task is done, run the full verification command, read the complete output and exit code, and only state success with that evidence attached.

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 entire output including exit code, and only then state the result with that evidence. Never commit based on previous runs or assumptions.

What counts as evidence that tests pass?▼

Only the actual test command output showing zero failures counts as evidence. Previous runs, partial checks, linter results, or confidence that the code should pass are not sufficient proof.

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. A test that never fails proves nothing.

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

No. Agent success reports must be independently verified by checking the version control diff and confirming the actual changes match the claimed work before reporting completion.

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

Linters check style and static patterns but do not compile code. A build claim requires running the actual build command and confirming exit code 0, since compilation errors are invisible to linters.

Related Skills

Explore More Software Engineering Skills→
LerianStudioLerianStudio
205

verification-before-completion

Require fresh verification command output before claiming task completion.

Official
Basic
SeanChenRSeanChenR

verification-before-completion

Require fresh verification commands and output inspection before completion claims.

Community
Intermediate
ludotypeludotype
1

verification-before-completion

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

Community
Basic
AndreaCadonnaAndreaCadonna

cicd-pipeline

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

Community
Advanced