proof
Skill249 starsChanged 14 days agoMITView on GitHub
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs
17 other projects use a version of this.
Adopted by
Most recently taken up by
- dimsedra/skillstheir own version, first seen Nov 8, 2026
- luci-efe/skillstheir own version, first seen Nov 1, 2026
- vijaysuperpositionist/skillstheir own version, first seen Nov 1, 2026
- ericmasiello/skillstheir own version, first seen Oct 20, 2026
- senlindesign/prooftheir own version, first seen Oct 17, 2026
- The-Utopia-Studio/skillstheir own version, first seen Oct 13, 2026
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- FlatbreadLabs/flatbread★ 69same name
- saschb2b/skills★ 22same name
- senlindesign/proof★ 17same name
- Sanexxxx777/curated-claude-code★ 16same name
- udaysharmadev/Skills★ 12same name
- The-Utopia-Studio/skills★ 6same name
- uda-eth/proof-skill★ 4same name
- CodeWithBehnam/cc-docs★ 2same name
- dimsedra/skills★ 2same name
- ssamba1/repo-proof★ 1same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- commands/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/feature-worktrees.mdcCursor rule
- .cursor/rules/no-cursor-commit-notes.mdcCursor rule
- diagnosisSkill
- draftingSkill
- feature-prototypeSkill
- inventingSkill
- mvp-prototypeSkill
- shippingSkill
- swarmSkill
- testingSkill
- using-superliteSkill
- writing-specsSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Run it fresh, or reuse a result only if nothing changed since that green run.
- Distinctive: line 21
Read the 2 to 3 lines the claim rests on: the counts, the exit code, the failure ids.
- Very specific: line 27
Run bash <skill-dir>/../swarm/scripts/superlite-cli run_tests --full for full suites (or --fast PATHS for a focused run).
“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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) frombash <skill-dir>/../swarm/scripts/superlite-cli run_tests --fullafter the last change. - 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
- Name the command that proves the claim.
- Run it fresh, or reuse a result only if nothing changed since that green run. If nothing changed, do not re-run.
- Read the 2 to 3 lines the claim rests on: the counts, the exit code, the failure ids. Not just "no error scrolled by".
- State the result honestly: "47 passed, 0 failed (run_tests --full, after the last edit)", or the actual failures.
- 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 --shortandgit diff --stat, and read the evidence it reports.
Full-suite runs
Run bash <skill-dir>/../swarm/scripts/superlite-cli run_tests --full for full suites (or --fast PATHS for a focused run); it prints one summary line, so logs stay out of your context. Run it once per wave and 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.