repro
Skill1 starsChanged 4 months agoMITView on GitHub
Turn a vague bug report into a minimal, runnable reproduction. Use when the report is "it crashes sometimes" / "it's broken on some inputs" and the fix needs the smallest script or test that reliably triggers the bug first.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- TestBeagle/TestBeagletheir own version, first seen Oct 20, 2026
- Whosnoory/greenprinttheir own version, first seen Oct 13, 2026
- vaadin/web-componentstheir own version, first seen Oct 8, 2026
- TPN-Labs/ClaudeSkillstheir own version, first seen Jun 22, 2026
- ucsandman/DashClawtheir own version, first seen May 14, 2026
- getsentry/reprotheir own version, first seen Jan 28, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- vaadin/web-components★ 585same name
- ucsandman/DashClaw★ 318same name
- getsentry/repro★ 2same name
- TestBeagle/TestBeagle★ 2same name
- Whosnoory/greenprint★ 2same name
- TPN-Labs/ClaudeSkills★ 0same name
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.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Search for the error message → the throwing site → walk backwards to every path that can reach it.
“Common” is measured: kept by at least 6 in 10 of the 6 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
Repro
A bug you can't reproduce is a rumor. Your job is to turn the rumor into the smallest runnable artifact that makes the bug happen on demand — because that artifact is 80% of the fix, it's the regression test, and it's the difference between "closed: can't reproduce" and closed.
Phase 1 — Interrogate the report (and the code)
Extract every concrete fact from the report: exact error text, the feature/action involved, timing ("sometimes", "after a while", "since the update"), environment hints. Then interrogate the codebase, which usually knows more than the reporter:
- Search for the error message → the throwing site → walk backwards to every path that can reach it.
- For each path, ask what input or state makes it fire. Each answer is a hypothesis.
- Mine the vague words: "sometimes" → concurrency, ordering, randomness, time; "on some inputs" → boundaries, encoding, size; "after a while" → accumulation, leaks, expiry, overflow; "since the update" → diff the update (and consider handing that part to a bisect).
Rank hypotheses by likelihood × ease of testing.
Phase 2 — Hunt
Build a harness that invokes the suspected code path directly — not the whole app — and try hypotheses in ranked order. Escalate only as needed:
- Deterministic candidates first: boundary inputs, malformed data, empty/huge/unicode.
- Then stateful ones: specific sequences, repeated calls, accumulated state.
- Then nondeterministic ones: tight loops for races, controlled seeds for randomness, frozen/advanced clocks for time bugs. For intermittents, crank the trigger conditions (parallelism, iteration count) until failure is reliable, then record the exact recipe.
- Instrument when hypotheses run out: assertions and logging at the suspect path to catch the state at failure time, then work backwards from the caught state.
First trigger is not the finish line — a repro that fires 1-in-20 is a lead, not a deliverable. Keep tightening until it fires every run (or document the honest rate and the conditions that maximize it).
Phase 3 — Minimize
Delta-debug the trigger down: remove every line, dependency, config flag, and data field that isn't needed for the bug to fire, re-running after each removal. The end state is the smallest input and shortest script that still reproduces — small enough to paste into an issue, obvious enough that the root cause is often visible in the repro itself.
Phase 4 — Deliver
- The repro script — runnable with one command, self-contained, seeded/deterministic wherever possible.
REPRO.md— exact trigger conditions, expected vs. actual, failure rate if not 100%, environment requirements, and the root-cause pointer if the minimization exposed it (it usually does).- The regression test — the repro converted into the project's test framework, currently failing, ready to flip green with the fix.
If it won't reproduce
That's a report, not a failure: document every hypothesis tested and ruled out, the harnesses used, and what evidence from the reporter would discriminate between surviving hypotheses (exact version, the input file, a log with timestamps). Ruling out ten causes is progress, and the discriminating-evidence list turns "can't reproduce" into a specific, answerable ask.
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.

