prove-it
Skill2 starsChanged 8 months agoApache-2.0View on GitHub
Prove that the current implementation works. Runs tests, diffs behavior, validates correctness. Use after implementing a feature or fix to verify before marking complete.
28 other projects use a version of this.
Adopted by
Most recently taken up by
- peaknr35/shark-Tank-prooftheir own version, first seen Nov 15, 2026
- dundas/thinkruntheir own version, first seen Nov 9, 2026
- 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
Used with
Projects with it also use root-cause, challenge and 1 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.
Ingramradical235Skillroot-cause
Structured root cause analysis using WHERE (MECE decomposition) then WHY (causal structure diagrams) pipeline. Includes coin-flip detection, logical-leap detection, and vicious cycle intervention. Use when buffer enters YELLOW/RED, when metrics stall, or when Actions execute but don't produce results.
Also in 3 projects that use this
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
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
Other versions28 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 28
- nagi-studio/skills★ 470same name
- AlemTuzlak/skills★ 45same name
- Neko-Catpital-Labs/Invoker★ 21same name
- anotherben/claude-harness★ 7same name
- nadirali1350/vetted★ 5same name
- Xnadir/vetted★ 5same name
- SaudSatopay/bullseye★ 4same name
- peaknr35/shark-Tank-proof★ 3same name
- drewdrewthis/claude-skills★ 2same name
- dundas/thinkrun★ 2same name
18 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 repository14 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- commit-push-prSkill
- freshSkill
- goSkill
- grillSkill
- investigateSkill
- retroSkill
- saveSkill
- secreviewSkill
- statusSkill
- tddSkill
- teamSkill
- techdebtSkill
- test-and-fixSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 26 edited versions we read keep these.
8
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 11
Run a comprehensive verification of the current implementation.
- Distinctive: line 49
If this is a bug fix or refactor:
- Distinctive: line 51
Run the specific failing case and prove it now passes
- Distinctive: line 52
Run related edge cases to check for regressions
- Very specific: line 87
After /commit-push-pr to verify before the PR
- Distinctive: line 88
After Builder finishes any implementation
- Distinctive: line 89
After a bug fix to prove the fix works
- Distinctive: line 90
After a refactor to prove behavior is unchanged
- Distinctive: line 91
When you're suspicious something might be broken
“Common” is measured: kept by at least 6 in 10 of the 26 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 Works
Run a comprehensive verification of the current implementation. This is the most important quality practice — "prove to me this works."
Verification Steps
1. Detect What Changed
git diff --name-only HEAD~1..HEAD # last commit
git diff --name-only # unstaged changes
git diff --stat main..HEAD # full branch diff2. Run All Relevant Tests
Based on what changed, run the appropriate test suite:
Rust files changed:
cargo test 2>&1
cargo clippy -- -D warnings 2>&1Python files changed:
pytest -v 2>&1
ruff check . 2>&1Shell scripts changed:
shellcheck *.sh 2>&1Any files changed:
# Build check — does it compile/build cleanly?
# Run the project-specific build command3. Behavioral Diff
If this is a bug fix or refactor:
- Show the before/after behavior explicitly
- Run the specific failing case and prove it now passes
- Run related edge cases to check for regressions
4. Edge Case Probes
For the changed code, probe:
- Empty/null inputs
- Boundary values
- Error paths (does it fail gracefully?)
- Concurrent access (if applicable)
5. Verdict
Produce a clear verdict:
## Verification Verdict
**Status**: PROVEN / FAILED / PARTIAL
### Tests
- [Suite]: [X pass, Y fail, Z skip]
### Build
- Compile: PASS/FAIL
- Lint: PASS/FAIL (N warnings)
### Behavioral Check
- [What was verified and how]
### Regressions
- [None / List]
### Confidence
- [HIGH / MEDIUM / LOW] — [why]When to Use
- After
/commit-push-prto verify before the PR - After Builder finishes any implementation
- After a bug fix to prove the fix works
- After a refactor to prove behavior is unchanged
- When you're suspicious something might be broken
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.

