Verification Before Completion

This is discipline for the moment right before you say "done" or commit your work. It enforces a simple gate: identify the verification command, run it fresh, read the full output, confirm it actually proves your claim, then and only then make the claim. The iron law is no completion claims without fresh verification evidence. It's built from 24 failure memories where Claude shipped undefined functions, missed requirements, or broke trust by claiming success without proof. The tone is blunt because the problem is common: exhaustion, overconfidence, or trusting agent reports leads to saying "should work" instead of running the test. Use this when you catch yourself about to call work complete.

skills.sh installs: 302
GitHub stars: 33.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add davila7/claude-code-templates --skill verification-before-completion --agent claude-code

Installs into .claude/skills of the current project.

Files

Verification Before Completion

Overview

Claiming work is complete without verification is dishonesty, not efficiency.

Core principle: Evidence before claims, always.

Violating the letter of this rule is violating the spirit of this rule.

The Iron Law

NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

If you haven't run the verification command in this message, you cannot claim it passes.

The Gate Function

BEFORE claiming any status or expressing satisfaction:

1. IDENTIFY: What command proves this claim?
2. RUN: Execute the FULL command (fresh, complete)
3. READ: Full output, check exit code, count failures
4. VERIFY: Does output confirm the claim?
   - If NO: State actual status with evidence
   - If YES: State claim WITH evidence
5. ONLY THEN: Make the claim

Skip any step = lying, not verifying