issue-investigator

Root cause analysis for software bugs systematically investigates incidents using a structured, evidence-based process to identify underlying causes, apply observability, test hypotheses, and document findings to prevent future recurrence.

To investigate performance issues across services, apply a structured multi-sensor investigation loop: understand the problem, hypothesize, instrument the code, observe telemetry, and document the actionable root cause.

Yes, this structured debugging workflow applies cross-domain to codebase bugs, service incidents, and system misconfigurations by enforcing observability and hypothesis testing to reach actionable conclusions.

The best way to document debugging findings is through systematic knowledge capture during the investigation loop, recording hypotheses, instrumentation steps, and observations to improve future incident response and debugging efforts.

Start an issue investigation by explaining the initial symptoms to the AI, gathering available data to form a concrete problem statement, and then generating testable hypotheses for systematic observation.

Hypothesis testing matters when diagnosing complex software issues because it enforces an evidence-based investigation loop, preventing premature conclusions and ensuring the true root cause is identified through observability.