skills.rest
epicodic
epicodicCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

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

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

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 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 Catalog: Tables mapping 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 reported success". - 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 completion 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 the claim, run it fresh and in full, read the entire output including exit code, and confirm it matches the claim. Only then state the result, citing the evidence such as test counts or exit status.

What counts as evidence that tests pass?▼

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

How do I verify a regression test actually works?▼

Use a 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 only passes once is not verified.

Can I trust a linter passing as proof the build works?▼

No. A linter does not check compilation, so linter success is not build evidence. Run the actual build command and confirm it exits with code 0 before claiming the build succeeds.

Should I trust a sub-agent's report that a task succeeded?▼

No. Agent success reports must be independently verified by inspecting the version control diff and confirming the actual changes exist before reporting the real state of the work.

Related Skills

Explore More Software Engineering Skills→
yuichi176yuichi176

code-change-verification

Install dependencies, build, lint, typecheck, and test code changes.

Community
Intermediate
All-The-VibesAll-The-Vibes
50

land

Commit changes, push to the remote, and open a pull request for handoff.

Official
Advanced
aquariuscookaquariuscook

shift-left-testing

Integrate testing into requirements and design phases with TDD and CI/CD.

Community
Advanced
autoclaw-ccautoclaw-cc
1.7k

xhs-auth

Automate Xiaohongshu login status checks and QR or phone verification via CLI.

Official
Intermediate