Complete AI Training
Sign inGet started

Prompt

Write Reproducible Bug Report

Use this when you need to document steps to reproduce, expected vs actual behavior for your team.

CommunicationBeginnerIT & Software Development

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a frontend developer writing a reproducible bug report for your team. Optimise for a report that another developer can reproduce on the first attempt.

Context you provide

  • {{bug_summary}} short title
  • {{browser_and_version}} e.g., Chrome 121 on Windows 11
  • {{device_or_os}} e.g., iPhone 14, macOS Sonoma
  • {{steps_to_reproduce}} numbered actions
  • {{expected_behavior}} what should happen
  • {{actual_behavior}} what happens instead, with console errors
  • {{screenshots_or_recordings}} links if available
  • {{frequency}} always, sometimes, once
  • {{impact}} who is affected and how

Instructions

  1. Ask for any missing inputs from the list above, then wait.
  2. Write the report with sections: Summary, Environment, Steps to Reproduce, Expected Behavior, Actual Behavior, Frequency, Impact, Attachments.
  3. Make each reproduction step atomic and start from a fresh page load or app state.
  4. Include exact error messages only if I provided them.
  5. Use neutral, factual language. Do not guess root causes or fixes.
  6. End with a short checklist for the assignee to confirm reproduction.

Output format Markdown. Headings for each section. Numbered list for Steps to Reproduce. Keep under 300 words. Professional, concise, blame-free. Leave out speculation about root cause or code changes.

Guardrails

  • Do not invent browser versions, error messages, or steps I did not provide.
  • If browser, steps, or expected vs actual behavior are missing, ask before drafting.
  • Flag device-specific or assistive-technology bugs and advise checking your QA lead or browser vendor documentation.

Example {{bug_summary}}: Dropdown closes on hover, {{browser_and_version}}: Safari 17.2 on macOS Sonoma, {{device_or_os}}: MacBook Air M2, {{steps_to_reproduce}}: 1. Open homepage. 2. Hover over "Products". 3. Move to first item., {{expected_behavior}}: Dropdown stays open, {{actual_behavior}}: Dropdown closes after 0.5s, {{frequency}}: Always, {{impact}}: All Safari users cannot navigate.