skills.rest
bilacchi
bilacchiCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

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

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

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 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 Tables: Concrete mappings of 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 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 entire output including exit codes, and only then state the result with that evidence. Never claim success 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, or statements like "should pass" do not qualify as verification.

Does a passing linter prove the build succeeds?▼

No, a linter does not check compilation. Build success requires running the build command and confirming exit 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 it fails, then restore the fix and confirm it passes again. A test that never fails proves nothing.

Can I trust an agent's report that a task succeeded?▼

No, agent success reports must be independently verified. Check the version control diff to confirm actual changes were made before reporting the real state of the work.

Related Skills

Explore More Software Engineering Skills→
Rawgrowth-ConsultingRawgrowth-Consulting

test-driven-development

Enforce a test-driven development workflow with failing tests before production code.

Official
Intermediate
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