gh:debug

To debug systematically, you trace a full causal chain from the trigger to the symptom, validating the root cause with evidence before applying a fix. This approach ensures your debugging is evidence-based rather than driven by surface symptoms.

A causal chain in debugging is the complete sequence of events from the initial trigger to the final symptom. Building this chain ensures you identify the true root cause of bugs instead of patching isolated failures.

Start a structured investigation for failing tests by entering a phase-driven debugging workflow that guides you from initial triage to handoff. Describe the test failure to begin building the causal chain.

Yes, you can use memory context to recall task context and prior solutions during bug diagnosis. This integration accelerates root-cause analysis by applying historical evidence to the current investigation.

Yes, phase-driven debugging works for issue-tracker investigations across codebases, teams, and environments. It provides guardrails to navigate from triage to a validated fix regardless of the environment context.

The best way to hand off an unresolved bug is to provide a structured report including the root cause, proposed fixes, tests, and prevention notes. This structured handoff accelerates remediation for the receiving engineer.