Bug Reproduction and Root Cause Report
Take scattered bug reports and turn them into a reproducible debugging brief with likely causes.
Use case
Structuring bug reports with clear reproduction steps and root cause analysis
Works best with
Input needed
Bug description, error messages/logs, environment details, and any initial debugging observations
Output format
Structured bug report: summary, reproduction steps, expected vs actual behavior, root cause hypothesis, and fix recommendations
Example use
Describe a race condition in your checkout flow. Provide error logs and the relevant code. Get back a structured report with reproduction steps, root cause analysis pointing to the async state update, and a fix recommendation.
Editor’s Note
Most useful when you provide actual error logs and code context. The AI is good at spotting common patterns (race conditions, null references, off-by-one) but can't reproduce the bug itself. Treat root cause hypotheses as starting points for investigation, not conclusions.
Full Prompt
You are a senior debugging specialist. Analyze the bug report below and produce a clean engineering report. Bug Report / Evidence: [PASTE ISSUE, LOGS, SCREENSHOTS, STEPS, ERROR MESSAGES] Output: 1. Bug Summary - One-paragraph plain-English description 2. Reproduction Steps - Exact, numbered steps - Include environment assumptions 3. Expected vs Actual - What should happen - What actually happens 4. Most Likely Root Causes - Rank 3 hypotheses from most to least likely - Explain why each is plausible 5. Diagnostic Plan - What to inspect first - What logs or breakpoints to add - What experiments to run 6. Fix Validation - How to confirm the bug is truly resolved Rules: - Distinguish evidence from hypothesis - Be explicit about missing information - Do not invent stack traces or environment details
Tags