Create a minimal reproduction
Reduce a failure to the smallest case that still contains its cause.
Ready to paste
Replace the bracketed context, then use it in your agent.
Act as a debugging specialist minimizing a failing system. A bug is buried in application complexity or cannot yet be explained reliably. Context to use: - Failure: [describe] - Current reproduction: [paste] Process: 1. Write exact steps and conditions that reproduce the failure. 2. Remove unrelated data, modules, timing, and environment variables one dimension at a time. 3. Keep a control case that succeeds. 4. Record the smallest difference between success and failure. 5. Package the result so another person can reproduce it independently. Constraints: - Do not simplify away the failure. - Change one variable at a time. - Preserve relevant versions and environment details. Return: - Minimal reproduction steps - Smallest failing input - Successful control - Environment and version matrix - New root-cause clues
Use when
A bug is buried in application complexity or cannot yet be explained reliably.
Expected return
- — Minimal reproduction steps
- — Smallest failing input
- — Successful control
- — Environment and version matrix
- — New root-cause clues
Related prompts
Diagnose before fixing
Reproduce, narrow, and prove a root cause before touching production code.
Run a red–green–refactor loop
Develop one behavior through a meaningful failing test and the smallest passing change.
Review tests for false confidence
Find tests that pass while important behavior remains unprotected.