PromptDev
Write a bug report
A prompt for turning messy observations into a proper bug report with steps, expected vs actual behaviour, and missing info flagged.
Last updated
Fill in the blanks
Assembled in your browser — nothing you type is stored or sent anywhere.
Your prompt
Turn these messy observations into a proper bug report: [paste the raw notes, Slack messages, or user report here].
Structure it as: a title naming the symptom and where it happens (like "Checkout: 500 after applying an expired coupon on mobile Safari", never "bug in checkout"); numbered reproduction steps in the order they must happen; Expected vs Actual behaviour, stated as two separate lines; Environment (browser, OS, app version, account type — whatever is known); and a severity rating with one sentence justifying it (who's affected, how often, whether there's a workaround). If the observations don't give enough to fill a section — reproduction steps, environment, or frequency — list what's missing as explicit questions at the end instead of inventing plausible-sounding steps.
Model-agnostic — works in Claude, ChatGPT, Gemini or any AI chat.
Why this prompt works
- →Requiring a symptom-and-location title instead of a vague one is what keeps a bug tracker searchable months later, rather than full of reports all called "issue with form."
- →Splitting Expected vs Actual into two explicit lines forces the report to state the assumption being violated — the part a rushed bug report skips most often.
- →Listing missing information as questions, instead of filling gaps with invented steps, stops a report from shipping false reproduction steps that send an engineer chasing the wrong scenario.