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.