Systematic Debugging

The key to systematic debugging is patience and thoroughness at each phase. Don't skip steps or jump to conclusions. Document everything you learn, even what doesn't work.

<anti_patterns> Skip directly to code changes without understanding Make multiple changes at once (can't identify which fixed it) Don't document the debugging process Fix symptoms while leaving root cause intact Assume fix works without verification </anti_patterns>

<integration_notes> When debugging with Claude Code, use phrases like:

• "Help me debug [issue] systematically"
• "I'm seeing [error], let's work through it methodically"
• "Let's isolate where this bug is occurring"

Claude will guide you through all four phases, prevent jumping to conclusions, help document findings, suggest targeted tests, and ensure proper verification. </integration_notes>

<related_skills> test-driven-development first-principles-thinking deep-research </related_skills>