Debugging a Bug

Debugging a Bug

The Flow

User: "Fix this bug..." / "This is broken..." / "Why doesn't this work..."

→ code-foundations classifies as DEBUG
→ cc-developer-character checks mindset (understand before fixing)
→ cc-quality-practices applies Scientific Debugging Method

Scientific Debugging Method

1. Form a hypothesis - "I think X is happening because Y"
2. Verify the hypothesis - Search, read, grep to confirm
3. Fix with confidence - You know WHY it works, not just THAT it works

What the Skill Prevents

Without Skill	With Skill
Trial-and-error debugging	Hypothesis-driven debugging
"Let me try this..."	"I think X because Y, let me verify"
Hours of random changes	Minutes of targeted investigation
Fix that might break something else	Fix you understand completely

Example Prompt

User: The picker window opens but the input doesn't have focus. Can you fix it?

Claude will:

1. Classify as DEBUG
2. Read the relevant code first
3. Form hypothesis: "The focus code is finding the wrong element"
4. Verify: grep for inheritance, confirm hypothesis
5. Fix: Add dedicated focus method

See It In Action

• Picker Focus Bug - Scientific Debugging Method in 57 seconds
• Picker Text Overflow - Root cause analysis with comparison table

Skills Involved

Skill	Role
code-foundations	Classifies task as DEBUG
cc-developer-character	"Understand before fixing" mindset
cc-quality-practices	Scientific Debugging Method