bug-diagnosis

To document debugging evidence, create a structured BugDiagnosis artifact capturing symptoms, reproduction steps, affected components, and probable causes before attempting a fix. This approach ensures you analyze evidence systematically rather than jumping straight into patching code.

Root-cause analysis for software bugs is a structured diagnosis process that identifies the underlying source of unstable behavior. You need it when symptoms are unclear, reproduction is flaky, or when you must document evidence and probable causes before engineering a solution.

To troubleshoot a flaky test, follow a guided workflow to narrow the affected area, gather concrete evidence, and rank plausible root causes. This systematic diagnosis generates a verification plan to ensure the identified cause is accurate before fixing.

Yes, this bug diagnosis process works without external dependencies. It formalizes the diagnosis phase by guiding you through capturing symptoms and reproduction steps natively, generating a comprehensive artifact that ranks plausible causes and outlines a verification plan.

The best way to structure a bug report for runtime errors is using a comprehensive BugDiagnosis format. It covers symptoms, reproduction status, affected components, gathered evidence, likely causes, next fix direction, and a verification plan to ensure thorough troubleshooting.

You should diagnose a bug thoroughly before fixing to ensure symptoms are captured, reproduced, and analyzed. This prevents patching incorrect probable causes, providing a structured artifact with evidence and a verification plan to guide the actual fix direction.