prove-it
Skill2 starsChanged 20 days agoMITView on GitHub
Give every critical path a test that dies under a behavior-changing mutation. Map the untested critical surface (coverage × call-graph of the money/auth/data paths), write characterization tests that assert real behavior, prove each earns its keep by failing at its assertion under a mutation (harness still runnable — a compile break is not proof), and route surfaced bugs to a fix or backlog, looping until every confirmed critical path is mutation-audited. Use when "close the test gap", "cover the critical paths", "pin a characterization net", "test debt", "add tests before we refactor", characterization/mutation testing, missing coverage. Not for broken tests, nor flake eradication (deflake-it), a deterministically failing test (clean-sweep), building features with tests from the start (ship-it), or restructuring a module's interface once the net exists (reshape-it — its DEEPEN units consume this mission's characterization net).
27 other projects use a version of this.
Adopted by
Most recently taken up by
- ryanda9910/prove-ittheir own version, first seen Nov 8, 2026
- decebal/chief-of-staff-v2their own version, first seen Nov 8, 2026
- SaudSatopay/bullseyetheir own version, first seen Nov 8, 2026
- anotherben/claude-harnesstheir own version, first seen Nov 8, 2026
- SylphxAI/skillstheir own version, first seen Nov 1, 2026
- nagi-studio/skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use challenge, grill and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
michalattSkillchallenge
Pressure-test plans, decisions, and directions by picking and answering the most relevant challenge questions for the current conversation
Also in 3 projects that use this
renatorozasSkillgrill
Adversarial code review. Don't let me ship until the changes pass your scrutiny.
Also in 4 projects that use this
AWSSkillretro
Conduct a retrospective on a coding session.
Also in 3 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
GoogleSkilltdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Also in 3 projects that use this
Other versions27 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 27
- nagi-studio/skills★ 470same name
- AlemTuzlak/skills★ 45same name
- Neko-Catpital-Labs/Invoker★ 20same name
- anotherben/claude-harness★ 7same name
- nadirali1350/vetted★ 5same name
- Xnadir/vetted★ 5same name
- SaudSatopay/bullseye★ 4same name
- drewdrewthis/claude-skills★ 2same name
- dundas/thinkrun★ 2same name
- duvi-ai/skills★ 2same name
17 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 repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- absorb-itSkill
- access-itSkill
- attest-itSkill
- clean-sweepSkill
- deflake-itSkill
- document-itSkill
- field-test-itSkill
- floor-itSkill
- harden-itSkill
- map-itSkill
- migrate-itSkill
- modernize-itSkill
- offload-itSkill
- oncall-itSkill
- oss-contributeSkill
- pin-itSkill
- reshape-itSkill
- review-itSkill
- root-causeSkill
- ship-itSkill
- speed-itSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 25 edited versions we read keep these.
1
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
- Very specific: line 74
Every critical-surface path: a merged test that fails at its assertion under a behavior-changing, harness-preserving mutation (the audit …
- Distinctive: line 77
Every surfaced bug: fixed-with-test, or parked with a reason, or handed to clean-sweep.
“Common” is measured: kept by at least 6 in 10 of the 25 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
prove-it — a mutation-audited test on every critical path
You are the COORDINATOR. Here the work CREATES PROOF where no defect finding necessarily exists;
the denominator is a FINITE CRITICAL SURFACE, done is MUTATION-SENSITIVE coverage of it, and bugs
surfaced during characterization spawn a NESTED remediation loop. Composes characterize, build-change, design-twice (choosing the
seam to pin), remediate-finding (for surfaced bugs), acceptance-review, runtime-prove, compound-learn;
rides merge-serialization, reviewed-sha-freshness, dispatch-lifecycle, liveness-resume,
evidence-manifest, ledger-contract, sandbox-policy, attention-budget. Worker TASK pack: one of matt | addy
— never co-mount.
DEFERRED READS, never at activation: mutation-hunt.md at build-blind REVIEW — the reviewer writes its
OWN killer mutant per path (PROFILE=rw, scratch clones only, commits nothing), so a builder's audit is never self-graded.
Two terminal outcomes
- COVERED — every path on the confirmed critical surface has a merged, mutation-audited test; every surfaced bug fixed-with-test.
- COVERED-WITH-PARKED (degraded) — all writable paths mutation-audited, ≥1 surfaced bug parked as needs-human (load-bearing quirk / behavior-change decision) or a path can't be tested without a human decision. Never reported as COVERED.
Pipeline
MAP critical surface (coverage gaps × call-graph of money/auth/data/external-contract entry points;
uncovered trivial getters are NOT the mission) → HUMAN scope confirm (bounds the mission)
→ BOOTSTRAP integration BASE (runtime/scripts/preflight.py --mission prove-it --base <BASE> --fork-point <sha
recorded in the ledger header at BASE creation>; BASE ≠ default — dispatch-lifecycle.md)
→ CHARACTERIZE waves (build-change, characterize): assert REAL expected behavior, and earn each
net with the mutation `characterize` specifies. Two outcomes:
· code correct, untested → the test passes; PROVE it per characterize.md, and record the audit's
`binding_audit` alongside the `negative_control` that playbook defines.
· test reveals a BUG → SURFACED-BUG sub-loop (remediate-finding). Route small clear fixes in-PR;
route ambiguous / behavior-changing bugs to PARK needs-human or hand to clean-sweep. Never assert
the buggy behavior as correct.
→ build-blind REVIEW (acceptance-review + mutation-hunt) → RUNTIME-PROVE (characterization asserts behavior the
real entry point actually exhibits, not harness-only fiction) → LAND
→ RE-MAP coverage → loop → outcome → REFLECT (`compound-learn`)Waves respect attention-budget WIP.
Convergence proof
Every critical-surface path: a merged test that fails at its assertion under a behavior-changing,
harness-preserving mutation (the audit recorded as negative_control + binding_audit; the verifier
re-runs the pinned mutant on a sample — ≥10% rounded up, the evidence-manifest §3 floor).
Every surfaced bug: fixed-with-test, or parked with a reason, or handed to clean-sweep. No assertion
weakened to pass (diff-audit). Coverage before/after pasted — but the pass criterion is the
mutation-audit set, not the percent. Manifest names COVERED or COVERED-WITH-PARKED.
Ledger + supervision
Header per liveness-resume.md: RUN · COORDINATOR · BASE · FORK_POINT · T0 · SOURCE · WIP (- if N/A;
SOURCE = critical-surface digest). Rows include Orca task id + path fields (test · mutation · PR ·
disposition). Stalls → WATCH; death → RESUME scoped to header coordinator + ledger task ids,
git-verified.
Anti-patterns
Chasing coverage percent (100% with tautological asserts proves nothing). A green test whose mutation passes (insensitive to the behavior — worse than no test). Accepting a compile break as the mutation proof. Silently asserting a surfaced bug's wrong behavior as correct. Unbounded surface (needs the confirmed critical list).
Related
deflake-it (test stability), clean-sweep (surfaced bugs go there), ship-it (build tests into new work).
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.

