bug-repro
Skill1 starsChanged 2 months agoMITView on GitHub
Turn a vague bug report into a minimal, deterministic reproduction and a failing regression test before any fix is attempted. Use when handed a bug report, a support ticket, a screenshot of an error, or "it doesn't work" with no steps.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- sabirmgd/terminal-first-goal-looptheir own version, first seen Sep 3, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- sabirmgd/terminal-first-goal-loop★ 2same 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.
In this repository34 other files it gives its agents.
- a11y-auditSkill
- api-contract-testingSkill
- autonomous-explorationSkill
- chaos-resilienceSkill
- ci-wiringSkill
- contract-testing-pactSkill
- coverage-ratchetSkill
- database-testingSkill
- e2e-authoringSkill
- environment-paritySkill
- exploratory-chartersSkill
- false-positive-hunterSkill
- flake-forensicsSkill
- i18n-l10n-testingSkill
- load-and-stressSkill
- mutation-proofSkill
- never-break-prodSkill
- payment-testingSkill
- perf-budgetSkill
- qa-triageSkill
- regression-curationSkill
- release-gateSkill
- responsive-mobile-testingSkill
- risk-mapSkill
- root-cause-protocolSkill
- security-regressionSkill
- smoke-and-sanitySkill
- state-machine-testingSkill
- test-data-managementSkill
- test-strategySkill
- tracking-testingSkill
- transactional-email-testingSkill
- unit-test-authoringSkill
- visual-regressionSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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 41
Only now hand off to the fix.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Bug Reproduction
A bug you cannot reproduce is a bug you cannot prove you fixed. This skill produces two artifacts: the smallest set of steps that trigger it, and a test that fails because of it.
Extract the report
From whatever you were given, fill these six fields. Missing fields are questions to ask, not blanks to imagine:
| Field | Example |
| Environment | prod, Chrome 141, macOS, tenant acme |
| Account/role | admin vs member — most "works for me" cases die here |
| Exact steps | numbered, one action per line |
| Expected | what the user believed would happen |
| Actual | including the exact error text and any request id |
| Frequency | always / N of M / only after X |
Reproduce, then minimize
- Reproduce it once, exactly as reported. Nothing is real until this happens.
- Minimize by bisection: remove one step, re-run. Keep removing while it still fails.
- Narrow the data: smallest payload, fewest rows, shortest string that still triggers it.
- Narrow the layer: does the API alone reproduce it without the UI? Then it is not a UI bug, and the regression test belongs at the API level — cheaper and faster forever.
- Record the minimal repro verbatim, including the seed data required.
Write the failing test first
RED tests/api/orders.spec.ts:88 "webhook retry creates a second charge"
-> 1 failed ✓ (the bug is now encoded)Only now hand off to the fix. After the fix, the same test must go green — and it must be
possible to make it red again by reverting the fix (mutation-proof). Without that, you fixed
something, but not provably this.
When it will not reproduce
Say so explicitly rather than guessing. Then attack the difference: data, permissions, timing,
cache, feature flags, browser, locale, timezone. Add logging around the suspected boundary and
ask for the request id from a real occurrence. An unreproduced bug stays open — never close it
as "cannot reproduce" while users are hitting it; escalate it to root-cause-protocol with
what you learned.
Output
REPRO 3 steps (from 11 reported), tenant seed: acme-min.sql
1. POST /webhooks/stripe with event id evt_1 -> 200
2. POST /webhooks/stripe with the same event id evt_1 -> 200
3. SELECT count(*) FROM charges WHERE event_id='evt_1' -> 2 (expected 1)
REGRESSION TEST tests/api/orders.spec.ts:88 -> failing as requiredDoes 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.