Systematic Debugging
调试类
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
Quick Start
Understand in 30 Seconds
Random fixes waste time and create new bugs.
Core Principle: Always find root cause before attempting fix. Symptom fixes are failure.
When to Use
- Test failures
- Production bugs
- Unexpected behavior
- Performance issues
- Build failures
Complete Guide
Iron Law
No fix without root cause investigationFour-Phase Process
Phase 1: Root Cause Investigation
- Read error message carefully
- Reproduce consistently
- Check recent changes
- Trace data flow
Phase 2: Pattern Analysis
- Find working example
- Compare with reference
- Identify differences
Phase 3: Hypothesis and Test
- Form single hypothesis
- Minimal test
- Verify before continuing
Phase 4: Implementation
- Create failing test case
- Implement single fix
- Verify fix
Related Skills
Related Skills
- test-driven-development - Create failing test case