skills.rest
Pega88
Pega88COMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

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

Updated Aug 20, 2026
Search Tags:#code quality#testing#debugging#verification#evidence#ci#completion claims
One-click install
npx skills add https://github.com/Pega88/agy-superpowers --skill verification-before-completion-pega88
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/Pega88/agy-superpowers/tree/main/.agents/plugins/superpowers/skills/verification-before-completion
Command: npx skills add https://github.com/Pega88/agy-superpowers --skill verification-before-completion-pega88

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 false success reports and broken commits. This Skill enforces an evidence-before-claims discipline so no completion statement is made without fresh command output. ## Core Features & Use Cases - Verification Gate: Requires identifying, running, and reading the full output of the proving command before any success claim. - Failure Pattern Catalog: Maps common claims (tests pass, build succeeds, bug fixed) to the exact evidence required and what is not sufficient. - Rationalization Blocking: Lists red flags and excuses ("should work", "linter passed", "agent said success") and counters each with the required verification step. - 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 Ask the agent to verify the fix with fresh test output before claiming the task is complete.

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 completely, then read the full output including exit codes and failure counts. Only state the change works after the output confirms it, citing the evidence.

How to confirm a bug fix actually works?▼

Run a test that reproduces the original symptom and confirm it passes. For regression tests, verify the red-green cycle: the test must fail without the fix and pass with it.

Is a passing linter enough to claim the build works?▼

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.

Can I trust a subagent's success report without checking?▼

No, agent success reports must be independently verified. Check the version control diff to confirm the changes 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 "just this once" reasoning all violate the evidence-before-claims principle.

Related Skills

Explore More Software Engineering Skills→
tony30552001tony30552001

gstack-openclaw-investigate

Investigates bugs via root-cause analysis and produces a structured debug report.

Community
Advanced
matthiaskloftmatthiaskloft

ship

Commit code, create a pull request, and monitor CI status for merging.

Community
Advanced
krishnakanthb13krishnakanthb13
41

debug_issue

Identify root causes of defects before applying fixes.

Community
Advanced
autoclaw-ccautoclaw-cc
1.7k

xhs-auth

Automate Xiaohongshu login status checks and QR or phone verification via CLI.

Official
Intermediate