systematic-debugging

Root cause analysis identifies the underlying issue behind a bug rather than treating surface symptoms. This Skill guides you through a four-phase framework—root cause investigation, pattern analysis, hypothesis testing, and implementation—ensuring you understand why a problem occurred before applying fixes, which prevents recurring bugs and wasted rework.

Systematic debugging applies structured investigation to production failures, test failures, and integration problems. This Skill enforces a disciplined workflow that completes root cause investigation before proposing solutions, using anti-rationalization safeguards to resist quick patches under time pressure and ensure thorough problem understanding.

Yes. This Skill's four-phase framework is designed to work even during critical incidents. It includes explicit rules and anti-patterns that help you resist shortcuts and maintain focus on root causes rather than temporary workarounds, ultimately saving hours of thrashing and preventing costly re-work.

Skipping root cause investigation leads to symptom-fixing, which often introduces new bugs and requires repeated fixes as the underlying issue resurfaces. This Skill enforces Phase 1 completion before any solution, ensuring you understand the true problem and implement a robust fix that addresses the actual source.

Debugging anti-patterns waste time on wrong assumptions and incomplete investigations. This Skill builds in explicit safeguards and step-by-step guidance from Phase 2 through Phase 4 to help you recognize and avoid common pitfalls, keeping your investigation focused on evidence rather than intuition.

Yes. This Skill applies its four-phase root cause framework across test failures, production issues, and integration problems. The same structured investigation method guides you to the true source of any technical failure, regardless of whether it surfaces in tests, live systems, or cross-service interactions.