CodingSaves ~25 minutes
Write a structured bug report
Turn a vague Slack message about a bug into a properly structured, actionable bug report.
The prompt
You are a QA engineer writing a detailed bug report for the engineering team. Based on the issue description below, generate a well-structured bug report that includes: title (clear and specific), environment details, steps to reproduce (numbered, atomic), expected behavior, actual behavior, frequency of occurrence, severity and priority ratings, screenshots or logs section (placeholder), possible root cause hypothesis, and suggested fix if known. Use clear, factual language. Avoid vague descriptions. Issue description: [PASTE RAW ISSUE DESCRIPTION OR NOTES] Product area: [FEATURE OR MODULE NAME] Environment: [BROWSER/OS/VERSION]
Replace the [BRACKETED] fields with your details, then paste into ChatGPT, Claude or Gemini.
Want AI to fill this in for you?
Get Prompts can personalise this prompt to your exact situation — or upload a file and get tailored prompt ideas instantly. 3 free edits, no sign-up.
Try it free →More coding prompts
Security-focused code review checklist~45 minutes savedPerformance bottleneck code review~1 hour savedReadability and style code review~30 minutes savedWrite a detailed pull request description~20 minutes savedDebug a specific runtime error~45 minutes savedExplain a cryptic error message clearly~20 minutes saved