verification-before-completion

What problem does it solve?

This Skill prevents false claims of completion by mandating fresh, explicit verification evidence before asserting any work is done, fixed, or passing, ensuring honesty, preventing rework, and building trust.

Core Features & Use Cases

• Mandatory Verification Gate: Enforces running full verification commands and confirming output before any success claims are made.
• Anti-Rationalization: Explicitly counters excuses for skipping verification, even when tired or confident, ensuring disciplined practice.
• Evidence-Based Claims: Requires providing concrete evidence (e.g., test command output, exit codes) with every completion claim, fostering transparency.
• Use Case: Before committing code, creating a Pull Request, or telling your human partner a bug is fixed, use this skill to run all necessary tests and checks, ensuring your claim is backed by fresh, undeniable evidence.

Quick Start

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