Skip to content
Skills Library
Programming · Review & audit

verification-before-completion

/verification-before-completion

Use when about to claim work is complete, fixed, passing, or ready to integrate. Do NOT use to repeat checks without a completion claim or concrete doubt.

Repository
ai-settings ↗
Licence
MIT
Last repository change
14.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when about to claim work is complete, fixed, passing, or ready to integrate. Do NOT use to repeat checks without a completion claim or concrete doubt.

Original author description

Use when about to claim work is complete, fixed, passing, or ready to integrate. Do NOT use to repeat checks without a completion claim or concrete doubt.

How it works

  1. Gate
  2. Examples
  3. Limits
Original SKILL.md headings · 46 lines, 233 words
SKILL.md preview
---
name: verification-before-completion
version: 6.2.0
category: workflow
description: Use when about to claim work is complete, fixed, passing, or ready to integrate. Do NOT use to repeat checks without a completion claim or concrete doubt.
---

# Verification Before Completion

Claims require fresh evidence from the current state.

Read `../using-superpowers/references/risk-policy.md`.

## Gate

Before a completion claim:

1. Identify the observable claim.
2. Choose the smallest command or manual path that proves it at the relevant
   boundary.
3. Run it fresh.
4. Read the result and exit status.
5. Report the evidence and any unverified boundary.

The complete command means the complete chosen check, not the entire repository
suite. Verification scope follows risk.

## Examples

| Claim | Evidence |
|---|---|
| Focused behavior works | affected test or reproducible smoke path |
| Build succeeds | build command exits 0 |
| Bug is fixed | original reproduction no longer fails |
| Plugin is installed | plugin listing shows expected source and version |
| Requirements are met | final diff checked against the approved scope |

Do not substitute old output, a reviewer summary, lint for a build, or tests for
an untested user-visible boundary.

## Limits

- Run the affected check once after the final relevant change.
- Rerun only when the checked state changed or the first result was ambiguous.
- Run the full suite only for shared core, a release boundary, or an explicit
  request.
- Do not make a reviewer repeat checks already evidenced without a concrete
  doubt.

If verification fails, report the actual state. Do not soften it into a success
claim.
Files in this package (2)
  • CHANGELOG.md 1 KB
  • SKILL.md 2 KB

Versions

RepositoryScoreLicence
This page · tsergeytovarov/ai-settings100MIT
jjuraszek/pi-gauntlet100MIT
GanyuanRan/Aegis100MIT
mvschwarz/openrig100Apache-2.0
nikospavlopoulos/devops-mutant-powers100MIT
FrancoStino/opencode-skills-collection100MIT
foryourhealth111-pixel/Vibe-Skills100Apache-2.0
rootcastleco/rei-skills100MIT
Montinou/triqual100MIT

Database snapshot: 13.11.2026 · package version 0a00150df900 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100spot-verification-before-completion
    Use when about to claim work is complete, fixed, passing, verified, release-ready, or ready to commit, merge, publish, or hand off.
  • 90completion-verification
    Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated. Use this before saying something is done, fixed, or passing; before committing or opening a…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.