verification-before-completion

Enforces running verification commands and reading output before claiming work is complete.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/dchavez3395/Puchica-hydrogen --skill verification-before-completion-dchavez3395
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/dchavez3395/Puchica-hydrogen/tree/main/docs/superpowers/skills/openclaw-ports/verification-before-completion
Command: npx skills add https://github.com/dchavez3395/Puchica-hydrogen --skill verification-before-completion-dchavez3395

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 command, leading to broken builds, false status reports, and lost trust. This Skill blocks any completion claim until fresh command output proves it. ## Core Features & Use Cases - The Iron Law gate: No completion claims without fresh verification evidence — identify the proving command, run it fully, read the output and exit code, then claim only what the output confirms. - Failure pattern tables: Maps common claims (tests pass, build succeeds, bug fixed, dev server alive) to the exact evidence required versus insufficient proxies like previous runs or linter output. - Rationalization prevention: Counters excuses like "should work now", "just this once", or "agent said success" with mandatory re-verification, including red-green regression test cycles and VCS diff checks for delegated agent work. - Use Case: Before telling a stakeholder that a bug fix is complete, run the failing test, confirm it passes, revert the fix to confirm the test fails, restore it, and only then report the verified result. ## Quick Start Before claiming any task is finished, invoke this skill to identify the command that proves completion, run it, and report the result with 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 claiming success?▼

Identify the command that proves the claim, run it fresh and in full, read the complete output and exit code, then state the claim only with that evidence. Skipping any step counts as an unverified claim.

How to verify a regression test actually catches the bug?▼

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. A test that never fails proves nothing.

Can I trust a linter passing as proof the build works?▼

No. A linter passing is not proof of compilation or runtime success. Run the actual build command and confirm exit code 0, since linters do not check compilation or execution paths.

Should I trust an agent's success report without checking?▼

No. Verify delegated work independently by inspecting the VCS diff with git diff HEAD and confirming the actual changes match the claimed outcome before reporting completion.

Why is a running process not proof a dev server works?▼

A live process only shows the process exists, not that it serves requests. Send a real HTTP request and confirm a 200 response, since processes can be alive while serving errors or stuck.