jeff-skill-error-debugging-rca

Root-cause debugging requires documenting the symptom, reproducing the issue reliably, and tracing data flow to confirm the underlying cause before implementing any minimal fixes. This systematic approach prevents premature symptom-driven patches.

Diagnosing intermittent runtime errors requires systematic evidence gathering, pattern comparison, and hypothesis testing to identify the root cause. This structured debugging framework guides you through safe implementation only after confirming the exact failure mechanism.

To stop applying symptom-driven patches, use a four-phase framework: investigate root causes, analyze patterns, test hypotheses, and implement fixes. A debugging checklist enforces careful investigation and prevents premature patches on test failures.

Yes, root-cause analysis applies directly to intermittent issues by enforcing reliable reproduction and diagnostic evidence gathering. Pattern analysis and hypothesis testing then isolate the exact failure trigger before any code changes are applied.

You should not skip systematic debugging when facing test failures, runtime errors, or intermittent issues, as premature patches risk recurring problems. Always enforce root-cause confirmation and trace data flow before implementing minimal fixes.