systematic-debugging

Root cause investigation requires enforcing a systematic debugging workflow before applying fixes. This Skill guides engineers through four phases—root cause investigation, pattern analysis, hypothesis testing, and implementation—to ensure code defects are resolved at their source.

Systematic debugging applies a four-phase workflow to flaky tests and production incidents, enforcing root cause investigation and pattern analysis before implementation. It uses defense-in-depth practices with layered validation to prevent future regressions.

Yes, systematic debugging applies to performance issues by guiding engineers through root cause investigation, pattern analysis, hypothesis testing, and implementation. It enforces thorough tracing and defense-in-depth instrumentation before applying fixes.

Starting Phase 1 of root cause investigation means analyzing the code defect before proposing any fixes. You must complete this initial investigation phase, followed by pattern analysis, hypothesis testing, and implementation, to resolve the issue systematically.

Symptom-based fixes should be avoided whenever you face code defects, flaky tests, performance issues, or production incidents. Enforce root cause analysis and pattern analysis first to ensure the fix addresses the actual underlying problem.