systematic_debugging

Root cause debugging requires a structured investigation process rather than patching symptoms. This skill guides you through four phases: thorough investigation, pattern analysis, hypothesis testing, and targeted implementation to identify faulty logic.

To debug an unexpected test failure, follow a systematic investigation by gathering evidence and tracing data flow. Instead of randomly changing code, analyze execution patterns, test hypotheses, and implement a precise fix to the underlying logic.

Systematic troubleshooting works by mandating evidence gathering and data flow tracing across complex systems. It enforces a four-phase process that prioritizes pattern analysis and hypothesis testing over quick fixes to ensure accurate error resolution.

Yes, you can resist pressure to apply quick fixes during error handling. This skill includes specific rules and language designed to prevent shortcuts under time pressure, ensuring you thoroughly diagnose problems before implementing targeted fixes.

You should avoid patching symptoms and use a structured debugging process whenever a test fails unexpectedly or complex technical issues arise. It prevents wasted time and new bugs by ensuring the actual root cause is identified and fixed.