Turn a Bug Report into a Minimal Repro Script
Added 2026-10-30
Given the symptom and a guess, have the model write the smallest script that reproduces it and list the assumptions to confirm.
You will get a bug report (symptom, environment, steps) and my initial guess. Output: 1) a minimal repro script or test with as few dependencies as possible, runnable as-is; 2) the assumptions I must confirm in the real environment; 3) if it does not reproduce, three investigation paths ranked by likelihood; 4) which variables to watch after it reproduces to identify the root cause. Do not propose a fix before reproduction.
Site original
Chinese original
How to use
先复现再修，能省掉一半来回。
Try tweaking it
- Have it restate requirements and constraints before writing code.
- Ask for the smallest change plus a rollback path, not a full-file rewrite.
What you should get
- A minimal, runnable change with copy-ready code
- Impact list: which files and call sites must follow
Common mistakes
- Asking it to touch ten files at once, then losing track of what broke what.
- Pasting only the error, with no code or version, and getting an unfixable answer.
How to check the output
- The change runs, can be rolled back, and touches nothing unrelated.
- Edge cases (empty, oversized, concurrent) are covered or explained.
Where it works
- Good for: having it restate requirements and constraints, then propose the smallest runnable change.
- Watch out: include versions and a minimal reproduction with the error, or the fix may look plausible but not fit.