skills.rest
Tgoldi
TgoldiCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

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

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

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 code, lost trust, and wasted rework. 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: Preempts common excuses like "should work", "linter passed", or "agent said success" with explicit counter-rules. - 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 complete, run the relevant verification 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, such as the test suite or build command, run it fresh, and read the full output including exit codes. Only state the claim after the output confirms it, citing the evidence.

What counts as evidence that tests pass?▼

Evidence is the actual output of a freshly run test command showing zero failures. Previous runs, assumptions like "should pass", or partial checks do not qualify as verification.

Does a passing linter mean 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 the test fails, then restore the fix and confirm it passes again. A single passing run proves nothing.

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

No, agent success reports must be independently verified by inspecting the VCS diff and confirming the actual changes match the claimed work before reporting completion.

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
shygolyshygoly

springboot-verification

Automate Spring Boot verification with builds, static analysis, tests, and security scans.

Community
Advanced
paultyngpaultyng
9

verify-when-complete

Run fresh format, lint, build, and test verification for Go projects.

Community
Intermediate