Programming · Review & audit
proof
/proof
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs
For whom
- Author
- iha2 ↗
- Repository
- superlite ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
90/ 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.
Content25 / 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
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
Deprecation
No signals detected. Repository changed on 12.11.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, or passing, before committing or creating PRs
Original author description
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs
How it works
- Acceptable evidence
- Rules
- Full-suite runs
- Requirements and delegated work
- Red flags: stop and verify first
- Never claim
Original SKILL.md headings · 40 lines, 394 words
SKILL.md preview
---
name: proof
description: Use when about to claim work is complete, fixed, or passing, before committing or creating PRs
---
# Proof
Evidence before claims. Never say "done", "fixed" or "passing" without fresh proof from this session.
## Acceptable evidence
- The one-line summary (`passed failed skipped seconds`) from the finish run after the last change: `bash <skill-dir>/../swarm/scripts/superlite-cli run_tests --full --reuse` or `run_tests --affected --base <start sha>`, per the plan's `**Full suite:**`.
- Or a focused run you executed yourself after the last change, covering exactly what you claim.
- For a build, a lint or a type check: that command's exit status and summary line.
- For a bug fix: the original reproduction now passing, plus its regression test.
## Rules
1. Name the command that proves the claim.
2. Run it fresh, or reuse a result only if nothing changed since that green run. If nothing changed, do not re-run.
3. Read the 2 to 3 lines the claim rests on: the counts, the exit code, the failure ids. Not just "no error scrolled by".
4. State the result honestly: "47 passed, 0 failed (run_tests --affected, after the last edit)", naming which finish run applied,, or the actual failures.
5. Scope the claim to the evidence. A passing unit test does not prove the build works. A clean lint does not prove tests pass. An agent saying "DONE" does not prove the diff is right: check `git status --short` and `git diff --stat`, and read the evidence it reports.
## Full-suite runs
Run `bash <skill-dir>/../swarm/scripts/superlite-cli run_tests --full --reuse` for full suites, `--affected` for changed code only (or `--fast PATHS` for a focused run); it prints one summary line, so logs stay out of your context. Run it once at the end, not after every small edit.
## Requirements and delegated work
Re-read the plan or request and tick each requirement off against the code and tests. A green suite does not mean the spec is met. Confirm the files a subagent changed match what its task owned.
## Red flags: stop and verify first
- "Should work now", "probably fine", "I'm confident".
- Satisfaction before the check ("Great!", "Done!").
- About to commit, push or open a PR without a check.
- Trusting a report without looking at its evidence.
- "Just this once", or being tired and wanting to finish.
## Never claim
Success with failures you decided to ignore. Say what fails and why it is acceptable, or fix it.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · iha2/superlite | 90 | MIT |
| chris-peterson/fathom | 100 | MIT |
| gosuda/dalcom-skills | 100 | Apache-2.0 |
| carloshmartins/proof | 100 | Apache-2.0 |
| The-Utopia-Studio/skills | 100 | Apache-2.0 |
| udaysharmadev/Skills | 100 | MIT |
| ahgraber/skills | 100 | CC0-1.0 |
| saschb2b/skills | 100 | MIT |
| gvkhosla/compound-engineering-pi | 100 | MIT |
Database snapshot: 13.11.2026 · package version fa883e763daa (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
- 96skill-verification-gate
Use when about to declare work complete, fixed, passing, or done - 100ferrox-verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always - 100verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always - 100verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always - 100verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always - 100verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing, creating PRs, or moving to the next task