systematic-debugging

Root cause analysis identifies why a bug occurs rather than treating surface symptoms. This skill guides you through a four-phase framework—investigation, pattern analysis, hypothesis testing, and implementation—to ensure you understand the underlying issue before proposing fixes, preventing recurring bugs and rework.

Systematic debugging collects diagnostic evidence across all components, reproduces issues reliably, logs inputs and outputs at system boundaries, and verifies changes with minimal, traceable steps. This approach ensures you gather complete evidence before implementing fixes.

Start by reproducing the issue reliably, then check recent changes and gather evidence from all affected components. The four-phase workflow—root cause investigation, pattern analysis, hypothesis formation, and implementation—guides you from symptom to underlying cause.

Investigating root causes prevents random fixes that create new bugs and costly rework. Enforcing complete diagnosis upfront eliminates time-wasting cycles of symptom-patching and ensures solutions address the true problem, not surface effects.

Yes. This skill applies to any technical issue—test failures, production bugs, unexpected behavior, performance problems, and build or integration failures. The same four-phase framework guides diagnosis across all issue types.

Collect evidence across all components involved in the issue: log inputs and outputs at system boundaries, reproduce the problem reliably, track recent changes, and document patterns. This comprehensive approach ensures you identify root causes rather than local symptoms.