verification-before-completion

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

Updated Nov 1, 2024
One-click install
npx skills add https://github.com/mlorentedev/dotfiles --skill verification-before-completion-mlorentedev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/mlorentedev/dotfiles/tree/main/harness/skills/verification-before-completion
Command: npx skills add https://github.com/mlorentedev/dotfiles --skill verification-before-completion-mlorentedev

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, broken trust, and wasted rework. This Skill blocks any completion claim until fresh command output proves it. ## Core Features & Use Cases - The Iron Law gate: Requires identifying, running, and reading the full verification command output before any success claim, commit, PR, or task closure. - Failure pattern tables: Maps common claims (tests pass, linter clean, bug fixed, agent completed) to the exact evidence required and what does not count as proof. - Rationalization and red-flag detection: Lists excuses like "should work now" or "agent said success" and counters each with the required verification action. - Closing Pass checklist: Walks a five-item Definition of Done (debt, knowledge, board, review, evidence) with a verdict per item before declaring completion. - Use Case: Before creating a PR, the agent runs the full test suite, confirms 0 failures in the output, verifies the regression test fails without the fix, checks the ticket status, and only then reports completion with evidence. ## Quick Start Before you claim this task is done, apply the verification-before-completion gate: run the full test command, read the output, and report the result with 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 the claim, run it fresh and in full, read the entire output including exit code and failure count, then state the claim with that evidence. Skipping any step means the claim is unverified.

What counts as evidence that tests pass?

Only the output of the actual test command showing zero failures counts. A previous run, a partial check, a passing linter, or confidence that it should pass are explicitly not sufficient evidence.

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. A test that only passes once is unverified.

Can I trust an agent's success report without checking?

No. After an agent reports success, inspect the VCS diff to confirm the changes actually exist and verify them independently before reporting the real state. Trusting the report alone is a listed failure mode.

When should the verification gate be applied?

Apply it before any success or completion claim, expression of satisfaction, commit, PR creation, task closure, moving to the next task, or delegating to agents. It covers paraphrases and implications of success, not just exact phrases.