root-cause-analyzer

Root-cause analysis traces stack frames to identify where execution diverges from expected behavior. Provide the stack trace, error message, and affected files; the analysis pinpoints the exact line and explains why the bug occurs and how tests may have missed it.

Gather reproduction evidence: stack traces showing the call chain, error messages, names of affected files, and test outputs that failed. This evidence lets root-cause analysis trace execution flow, locate the divergence point, and document why coverage gaps exist.

Yes. Root-cause analysis traces execution and identifies divergence points regardless of codebase size or complexity. It documents file paths, line references, and explains failing behavior across interconnected modules and services.

Root-cause analysis examines the gap between test coverage and actual execution paths. It identifies missing test cases, incomplete assertions, or untested branches where the bug hides, explaining why existing tests failed to catch it.

Error messages show symptoms; root-cause analysis traces the call chain and execution flow to reveal the origin of the failure. It builds hypotheses about why the bug occurs and documents the exact conditions that trigger it, not just where it crashes.

A concise narrative with file paths, line numbers, and explanations of the bug's origin. The analysis also documents which test gaps allowed the bug to escape and what evidence was missing to catch it earlier.