systematic-debugging

Root cause analysis in software debugging is identifying the underlying defect before modifying code. This skill systematizes the process through a four-phase framework that enforces evidence-based hypothesis testing to ensure architectural integrity.

To fix intermittent production bugs without guessing, you build deterministic reproduction loops that validate symptoms. This skill directs the creation of high-repetition test harnesses to isolate failures and trace data flow for permanent fixes.

To troubleshoot performance regressions systematically, you follow a four-phase root cause analysis framework. This process requires constructing deterministic reproduction scripts and applying evidence-based hypothesis testing to resolve defects.

The best way to stop recurring bugs and technical debt is to replace quick-patching with an evidence-based debugging process. This skill enforces rigorous root cause identification through automated reproduction loops before any code changes.

Yes, you can use systematic debugging for failing test cases by following the four-phase process. The skill guides the construction of deterministic, automated reproduction scripts to validate symptoms and verify fixes within the current repository.

You should not use a quick patch for software defects when facing test failures or production bugs, as it leads to recurring issues. Instead, apply a structured root cause analysis framework to ensure a permanent fix.