verification-before-completion

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

Updated Jul 4, 2024

Search Tags:#code quality #testing #verification #evidence #regression testing #ci #completion claims

Ready to run

npx skills add https://github.com/hareki/dotfiles --skill verification-before-completion-hareki

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/hareki/dotfiles/tree/main/agents/.agents/skills/verification-before-completion
Command: npx skills add https://github.com/hareki/dotfiles --skill verification-before-completion-hareki

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 code, lost trust, and wasted rework cycles. ## Core Features & Use Cases - Evidence-First Gate: Requires identifying, running, and reading the full output of a verification command before any success 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 common excuses like "should work now" or "linter passed" and explains why each is insufficient. - Use Case: Before committing a bug fix, run the original failing test, confirm it passes, then state the result with the observed output instead of assuming the change worked. ## Quick Start Before claiming any task is complete, 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 including exit code, and only then state the result with that evidence. Never commit based on assumptions or previous runs.

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

Does a passing linter mean the build succeeds?▼

No, a linter only checks style and static patterns, not 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 report that a task succeeded?▼

No, agent success reports must be independently verified. Check the version control diff to confirm changes exist and run the relevant verification commands yourself before reporting the actual state.

When should verification before completion be applied?▼

Apply it before any success claim, expression of satisfaction, commit, pull request, task handoff, or delegation. The rule covers exact phrases, paraphrases, and any wording implying completion or correctness.