skills.rest
farslab
farslabCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verification-before-completion

Enforces running verification commands and checking output before making any completion claims.

Updated Aug 22, 2026
Search Tags:#code quality#testing#tdd#verification#evidence#ci#completion claims
One-click install
npx skills add https://github.com/farslab/claude-skills --skill verification-before-completion-farslab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/farslab/claude-skills/tree/main/verification-before-completion
Command: npx skills add https://github.com/farslab/claude-skills --skill verification-before-completion-farslab

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, broken commits, and wasted debugging time. ## Core Features & Use Cases - Evidence-First Gate: Requires identifying, running, and reading the full output of a verification command before any success claim is made. - Failure Pattern Detection: Flags rationalizations like "should pass", "linter passed", or trusting agent success reports without independent checks. - 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 state the fix works with the evidence attached. ## Quick Start Before claiming any task is done, run the relevant test or build command and report the actual output alongside your claim.

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 a previous run or assumption.

How to 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.

Does a passing linter mean the build succeeds?▼

No, a linter does not check compilation. You must run the actual build command and confirm it exits with code 0 before claiming the build succeeds.

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

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

When should verification be skipped for small changes?▼

Never. The rule has no exceptions for small changes, confidence, or time pressure. Partial checks and assumptions prove nothing, so run the full verification command every time.

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
SeanChenRSeanChenR

verification-before-completion

Require fresh verification commands and output inspection before completion claims.

Community
Intermediate
coco-decoco-de

code-review

Coordinates manual and automated checks for systematic code review across eight quality dimensions.

Official
Intermediate
tody-agenttody-agent
48

cm-quality-gate

Enforce test gates and evidence-based verification before deployment in CI/CD workflows.

Community
Advanced