systematic-debugging

Root cause analysis requires methodical investigation before applying any fix. This Skill guides you through a four-phase process: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation. Phase 1 focuses on understanding what actually failed, not patching it—preventing symptom-chasing that creates new bugs and rework.

Systematic debugging enforces a disciplined approach even when managers demand immediate fixes. It prevents frantic attempts that often worsen issues by requiring thorough root cause investigation before any implementation, ensuring lasting solutions instead of temporary patches.

This framework applies to test failures, production bugs, unexpected behavior, performance problems, build failures, and integration issues. It uses pattern analysis and hypothesis testing to identify the actual failure point, then implements verified fixes—not guesses.

Quick fixes address visible symptoms without understanding underlying causes, introducing new bugs and costly rework. Systematic debugging's anti-shortcut mechanisms force investigation of the true issue first, delivering robust remediation that doesn't regress.

Recovery workflows guide you when initial fixes fail, including when to stop and question the underlying architecture. Rather than trying random solutions, you return to root cause investigation with new evidence, applying the same disciplined phases.

Yes. Systematic debugging applies across test failures, production bugs, unexpected behavior, performance problems, build failures, and integration issues. The four-phase methodology works regardless of issue type—investigation, pattern analysis, hypothesis testing, then implementation.