skills.rest
kxnzee
kxnzeeCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

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

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

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 five-step gate function (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 is not sufficient. - 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 test or build 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 complete 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 sufficient evidence that tests pass?▼

Only the output of a freshly run test command showing zero failures counts as evidence. Previous runs, partial checks, linter results, or confidence that the code should pass are explicitly not sufficient.

Does a passing linter mean the build succeeds?▼

No, a linter passing does not prove compilation or build success. You must run the actual build command and confirm it exits with code 0 before claiming the build passes.

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

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 and run the relevant verification commands before reporting the real state.

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
basicmachines-cobasicmachines-co
4.0k

pr-create

Creates or updates Basic Memory pull requests and runs the Codex review loop.

Official
Intermediate
pascallammerspascallammers
1

debugging-systematic

Diagnose bugs through a four-phase root cause analysis framework.

Community
Advanced
sapatamuku-creatorsapatamuku-creator

ci-cd-and-automation

Configures CI/CD pipelines with quality gates, deployment strategies, and rollback workflows.

Community
Intermediate