skills.rest
chenziyang110
chenziyang110COMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

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

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

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 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: Defines a five-step gate (identify, run, read, verify, claim) that must be completed before any completion 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 Blocking: Lists common 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 the evidence attached. ## Quick Start Before claiming any task is done, run the relevant test or build command and report the actual output as evidence for the 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 the claim, run it fresh and completely, read the full output including exit code, 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 fresh output from the actual test command showing zero failures counts as evidence. Previous runs, partial checks, linter results, or confidence that the code should pass do not qualify as verification.

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

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

Linters check style and syntax patterns but do not compile or link code. A build claim requires running the actual build command and confirming exit code 0, since linter-passing code can still fail compilation.

Related Skills

Explore More Software Engineering Skills→
udayvunnamudayvunnam
246

nx-run-tasks

Execute build, test, lint, and serve tasks within an Nx workspace.

Community
Intermediate
caitengweicaitengwei
6

verification-before-completion

Require fresh command execution and evidence before reporting completion status.

Community
Basic
nateanatea

shift-left-testing

Validate requirements and generate tests earlier in CI/CD pipelines.

Community
Advanced
cncorpcncorp

test-runner

Run ruff, lint, and parallel mocked, e2e-live, and smoke tests.

Official
Intermediate