Prompt library
Turn a vague bug into a reproducible report
Confining hypotheses to their own section keeps the factual report trustworthy while still capturing debugging intuition. The [GAP] markers turn missing reproduction steps into a checklist instead of fabricated certainty, which is what makes another engineer able to act on it.
Last reviewed July 17, 2026
The prompt
Turn my messy bug notes into a reproducible bug report.
Notes: {{notes}}
Produce:
1. Title: symptom plus trigger in one line ("Export hangs when a filter contains an emoji").
2. Environment: version, platform, config that plausibly matters. Mark unknowns as unknowns.
3. Steps to reproduce: numbered, starting from a clean state, each step observable. If my notes skip a step, insert [GAP: what needs checking] rather than guessing.
4. Expected vs actual, one line each, plus exact error text if present.
5. Severity and blast radius: who hits this and how often, judged from the notes.
6. Repro confidence: deterministic, intermittent (with observed rate), or not yet reproduced.
7. Three most plausible hypotheses ranked, each with the cheapest experiment to confirm or kill it.
Keep speculation strictly inside section 7.Run in idaptOpens a new chat with the prompt prefilled. Nothing sends until you press send.
Fill in the variables
| Variable | What it is | Example |
|---|---|---|
| {{notes}} | Everything you know, unsorted | [paste your notes, logs, and screenshots description] |