Write a clear, reproducible bug report
Bug reports developers can act on immediately — steps, expected vs. actual, environment, and evidence.
The prompt
Turn my notes into a clear bug report.
What happened: [DESCRIPTION]
What I expected: [EXPECTED]
Steps I took: [STEPS, as best I remember]
Environment: [app version, device, OS, browser, account type]
Evidence: [error messages, logs, screenshots]
Write: a specific title (what is broken + where); severity and impact; numbered steps to reproduce; expected vs. actual result; environment; frequency (always / sometimes); evidence; and suspected cause or workaround if known. Mark anything I need to confirm as [CONFIRM].
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Software Development prompts
What to fill in
- DESCRIPTION
- EXPECTED
- STEPS, as best I remember
- app version, device, OS, browser, account type
- error messages, logs, screenshots
- CONFIRM
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Refactor code to be cleaner and easier to maintainImproves structure, naming, and design without changing behavior.
- Convert code to another language or frameworkIdiomatic translation of code between languages or frameworks, with notes on differences.
- Write unit tests for my codeComprehensive unit tests covering happy paths, edge cases, and failures.
- Write and explain a regular expressionBuilds a regex from a description, explains it piece by piece, and tests it.