# Verification Before Completion

> Use before claiming any work is complete, fixed, or passing — runs verification commands and confirms output before making success claims.

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

---


# Verification Before Completion

## Rule

Never claim "done", "fixed", or "passing" without running verification commands and showing the output.

Evidence before assertions. Always.

## Checklist

Before claiming complete:

- [ ] Run the test suite: show the output
- [ ] Run the linter/formatter: show the output
- [ ] Confirm the specific behavior that was requested works
- [ ] No regressions in previously passing tests

## What to Show

```
Tests: pytest output (N passed, 0 failed)
Lint: ruff/eslint output (clean)
Behavior: [description of manual or automated check]
```

If anything fails: report it honestly. Do not claim partial success as full success.