# Verification Before Completion

> Require evidence before claiming work is complete, fixed, or tests pass. Use before commits, PRs, or any "done", "fixed", "works now", "should work", or "tests pass" statement.

- Skill: `tsurai7/verification-before-completion` (Agent Skill)
- Install (CLI): `npx skillmds@latest add tsurai7/verification-before-completion`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tsurai7/verification-before-completion/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Tsurai7 (https://skillmd.com/u/tsurai7)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tsurai7/verification-before-completion

---


# Verification before completion

**No assertions without fresh verification evidence.**

## Gate

Do not claim completion until you have **run** the relevant check and **seen** successful output in this session.

## Required evidence

| Claim | Minimum evidence |
|-------|------------------|
| Tests pass | Test command output showing pass |
| Build succeeds | Build command exit 0 + output |
| Bug fixed | Reproduction steps pass after fix |
| Lint clean | Linter output on changed files showing zero errors |
| Test guards behavior X | The test fails when X is broken (bug reintroduced or mutated), then passes |

## Process

1. Identify the command that proves the claim
2. Run it (fix failures; do not lower the bar)
3. Read output — confirm success, not absence of errors
4. Only then state completion

## Red flags — stop and verify

- Using "should", "probably", "seems to"
- Reporting success before running the command
- Trusting a prior run after code changed
- "I'm confident" without command output

## Short form

```
CLAIM: [what you want to assert]
EVIDENCE: [command just run]
OUTPUT: [relevant success lines]
VERDICT: [claim supported only if output matches]
```

Keep this gate for every "done" statement.