skills.rest
AnderHonorato
AnderHonoratoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verification-before-completion

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

Updated Aug 28, 2026
Search Tags:#code quality#testing#verification#evidence#regression testing#build validation#completion claims
One-click install
npx skills add https://github.com/AnderHonorato/Mem-rias-IA---Infinity --skill verification-before-completion-anderhonorato
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/AnderHonorato/Mem-rias-IA---Infinity/tree/main/Manus/Skills/snapshots/superpowers-verification-before-completion
Command: npx skills add https://github.com/AnderHonorato/Mem-rias-IA---Infinity --skill verification-before-completion-anderhonorato

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, broken commits, and wasted debugging time. ## Core Features & Use Cases - Evidence-First Gate: Requires identifying, running, and reading the full output of a verification command before any completion claim is made. - Failure Pattern Catalog: Maps common claims (tests pass, build succeeds, bug fixed) to the exact evidence required and what does not count as proof. - Rationalization Blocking: Lists red flags and excuses ("should work", "just this once", "agent said success") with their counterarguments to prevent premature satisfaction. - Use Case: Before committing a bug fix, run the test suite, confirm zero failures in the output, and only then state the fix is verified with the evidence attached. ## Quick Start Before claiming any task is complete, 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 claim success based on a previous run or assumption.

What counts as evidence that tests pass?▼

Only the actual test command output showing zero failures counts as evidence. A previous successful run, confidence that it should pass, or a partial check does not qualify as verification.

Does a passing linter mean the build succeeds?▼

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

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.

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

Related Skills

Explore More Software Engineering Skills→
Nairon-AINairon-AI
7

flux-verify-claims

Execute proving commands and report real outcomes from exit statuses.

Official
Advanced
SeanChenRSeanChenR

verification-before-completion

Require fresh verification commands and output inspection before completion claims.

Community
Intermediate
Devsoul2026Devsoul2026
150

requesting-code-review

Automate pre-commit verification with static analysis, tests, and lint checks.

Community
Advanced
BruceTyndallBruceTyndall

dev-workflow-scheduler

Schedule and sequence development tasks into automated workflow pipelines.

Community
Advanced