skills.rest
CYRUS-pinto
CYRUS-pintoCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

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

Updated Sep 11, 2026
Search Tags:#code quality#testing#tdd#verification#evidence#build validation#completion claims
One-click install
npx skills add https://github.com/CYRUS-pinto/pi-bot --skill verification-before-completion-cyrus-pinto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/CYRUS-pinto/pi-bot/tree/main/.agents/skills/verification-before-completion
Command: npx skills add https://github.com/CYRUS-pinto/pi-bot --skill verification-before-completion-cyrus-pinto

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 false success reports and broken commits. This Skill enforces an evidence-before-claims discipline. ## Core Features & Use Cases - Verification Gate: Requires identifying, running, and reading the full output of a verification command before any completion claim. - Failure Pattern Catalog: Maps common claims (tests pass, build succeeds, bug fixed) to the exact evidence required and what is not sufficient. - Rationalization Prevention: Counters excuses like "should work", "linter passed", or "agent said success" with concrete verification requirements. - 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. ## Quick Start Before claiming any task is done, run the relevant test or build command and report the actual output as 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 and exit code, then only make the claim if the output confirms it. Never rely on previous runs or assumptions.

How to verify a regression test actually works?▼

Use the red-green cycle: write the test, run it to see it pass, revert the fix and confirm the test fails, then restore the fix and confirm it passes again. A test that never fails proves nothing.

Does a passing linter mean the build succeeds?▼

No, a linter does not check compilation. You must run the actual build command and confirm it exits with code 0 before claiming the build succeeds.

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 the changes actually exist and match the claimed work before reporting completion.

When should verification be skipped for small changes?▼

Never. The rule has no exceptions: partial checks, confidence, fatigue, or small change size do not substitute for running the verification command and reading its output.

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
tachiiri-orgtachiiri-org

release

Create a pull request from the dev branch to main after verifying branch and remote state.

Official
Intermediate
519lab519lab
2

requesting-code-review

Run automated code review with security scans and static analysis before commit.

Official
Advanced
mahg-esmahg-es
3

cicd-quality

Design and enforce CI/CD quality gates for code, tests, security, build, E2E, and performance.

Official
Advanced