skills.rest
ibytechaos
ibytechaosCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

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

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

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 builds, shipped defects, and lost trust. This Skill enforces an evidence-first discipline so no completion claim is made without fresh command output. ## Core Features & Use Cases - Verification Gate: Defines a mandatory five-step gate (identify, run, read, verify, claim) that must be completed before any success statement. - Failure Pattern Catalog: Maps common claims (tests pass, linter clean, build succeeds, bug fixed) to the exact evidence required and what does not count as proof. - Rationalization Blocking: Lists red-flag phrases and excuses ("should work", "just this once", "agent said success") that signal an unverified claim. - 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 Ask the agent to verify the fix by running the full test suite and only claim completion after confirming the output shows zero failures.

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 code changes before committing?▼

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 evidence. Never commit based on a previous run or assumption.

How to confirm a bug fix actually works?▼

Run a test that reproduces the original symptom and confirm it passes after the fix. Changing the code and assuming it is fixed is not sufficient evidence of resolution.

Does a passing linter mean the build succeeds?▼

No, a linter passing does not prove compilation succeeds. Linters check style and some errors but do not verify the build; you must run the actual build command and confirm exit code 0.

How do I verify a regression test really works?▼

Use the red-green cycle: write the test, 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. Check the version control diff to confirm actual changes were made and run the relevant verification commands yourself before reporting completion.

Related Skills

Explore More Software Engineering Skills→
ethicalcapitalethicalcapital

test-driven-development

Implement Test-Driven Development with a red-green-refactor cycle.

Official
Intermediate
basicmachines-cobasicmachines-co
4.0k

pr-create

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

Official
Intermediate
KimjimanKimjiman

springboot-verification

Automate build, static analysis, tests, security scans, and diff review for Spring Boot projects.

Community
Advanced
X-School-AcademyX-School-Academy
19

dev-swarm-stage-devops

Automate GitHub, CI/CD, Docker, and AWS infrastructure setup.

Official
Advanced