systematic-debugging

Root cause analysis identifies the underlying source of a bug rather than fixing surface symptoms. This skill guides a four-phase process—investigation, pattern analysis, hypothesis testing, and implementation—to ensure fixes address the actual problem, preventing recurring failures and deeper issues.

Systematic troubleshooting applies evidence-based investigation and diagnostic instrumentation to production incidents and test failures. This approach enforces finding the true source before implementing fixes, resisting pressure to apply quick patches that mask underlying architectural or design problems.

Structured debugging replaces trial-and-error with a disciplined framework that mandates root cause identification. It includes anti-pattern awareness and validation that your fix resolves the issue under various operating conditions, stopping symptom-chasing cycles.

If multiple fixes fail to resolve recurring issues, architectural problems may be the root cause. This skill prompts architectural review when symptom-focused solutions repeatedly fail, preventing endless patching and revealing design-level flaws.

Yes, systematic debugging applies to software issues including bugs, test failures, production incidents, performance problems, and integration glitches. The four-phase framework works across all these problem types to identify and resolve root causes.

This approach enforces evidence-based investigation and a no-symptom-fixes mandate, with explicit language designed to resist rationalization under time pressure. It ensures thorough diagnosis before implementation, distinguishing it from ad-hoc or shortcut-prone debugging practices.