Home
← Back to templates
Bug report
Programming
Turn a rough description of a problem into a structured bug report.
Related technique:Few-shot prompting
Write a bug report. Input: when I upload a PNG larger than 5MB on Safari, the progress bar freezes at 80% and nothing happens; works fine on Chrome; expected the upload to finish normally; happened 3 times today. Format: Bullet list
Expected output
A structured report: summary, steps to reproduce, expected vs. actual behavior, environment/frequency — ready to paste into an issue tracker.
Usage tips
- Include what you expected to happen, not just what went wrong — "expected vs. actual" is what makes a report actionable.
- Mention frequency/environment (browser, how often) whenever you have it; it's often the detail that unblocks debugging.
Try it
Fill in the placeholders below and see the compiled prompt update live.
The material to work from.
The structure of the output.
- 8
- Words
- 58
- Characters
- 0/2
- Placeholders filled
- 1 min
- Reading time
Quality score6
- Completeness0
- Clarity0
- Context0
- Specificity0
- Constraints0
- Format0
- Output0
- Constraints note0
- Success criteria0
- Scope focus100
- Verification step0
- Negative example0
- Confidence0
- Placeholder syntax100
- Markdown structure0
Suggestions
- Fill in the remaining placeholders.
- Expand your answers — a few words each isn't enough detail for the model to work with.
- Add background context so the model understands the situation.
Write a bug report.
Input: {{INPUT}}
Format: {{FORMAT}}
AI Assistant