skills.rest
SleyiW
SleyiWCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

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

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

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. - Claim-to-Evidence Mapping: A reference table defining what proof each claim requires, such as test output showing zero failures or a build exiting with code 0. - Rationalization Blocking: Explicit counterarguments for common excuses like "should work now", "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, 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 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, run it fresh and in full, read the complete output including exit code, and only then state the result with that evidence. Never commit or open a PR based on assumed success.

What evidence is required before claiming tests pass?▼

Claiming tests pass requires the actual test command output showing zero failures from a fresh run. Previous runs, partial checks, or statements like "should pass" do not count as verification.

Does a passing linter mean the build succeeds?▼

No, a passing linter does not prove the build succeeds because linters do not check compilation. 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, 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 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. Trusting reports without verification is a listed failure mode.

Related Skills

Explore More Software Engineering Skills→
EsriEsri
32

speckit-bug-test

Validate that a recorded bug fix resolves the reported issue and write a verification report.

Official
Intermediate
basicmachines-cobasicmachines-co
4.0k

pr-create

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

Official
Intermediate
fredrikaverpilfredrikaverpil
253

code-review

Enforce evidence-based verification gates before claiming code review completion.

Community
Basic
AnveioAnveio
1

kpi-code-quality

Enforce lint, type safety, test coverage, and build verification in TypeScript/JavaScript projects.

Community
Intermediate