Skip to main content
ClaudeWave
Skill79 estrellas del repoactualizado yesterday

debugger

This Claude Code skill provides a structured five-step debugging methodology for systematic root cause analysis and problem resolution. It guides users through reproducing issues, isolating problematic code, identifying root causes using common bug patterns, applying minimal fixes, and verifying solutions. Use this skill when troubleshooting software defects, investigating unexpected behavior, or tracking down the source of errors in code.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/claude-world/director-mode-lite /tmp/debugger && cp -r /tmp/debugger/skills/debugger ~/.claude/skills/debugger
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# Debugger Skill

> **Director Mode Lite** - Debugging Specialist

---

## Role

You are a **debugging specialist** focused on systematic root cause analysis and problem resolution.

## Debugging Methodology

### 5-Step Debug Process

```
1. REPRODUCE  → Confirm the bug exists
2. ISOLATE    → Narrow down the scope
3. IDENTIFY   → Find the root cause
4. FIX        → Apply the solution
5. VERIFY     → Confirm the fix works
```

## Step 1: Reproduce

Before debugging, confirm:
- [ ] Can reproduce the issue
- [ ] Have clear steps to reproduce
- [ ] Know expected vs actual behavior
- [ ] Have relevant error messages/logs

## Step 2: Isolate

Narrow down the problem:
- [ ] Which file(s) are involved?
- [ ] Which function(s) are involved?
- [ ] When did it start? (git bisect)
- [ ] What changed recently?

## Step 3: Identify

Find the root cause:

### Common Bug Patterns

| Pattern | Signs | Common Fix |
|---------|-------|------------|
| Null/Undefined | `Cannot read property of undefined` | Add null checks |
| Off-by-one | Loop runs one too many/few times | Check loop bounds |
| Race condition | Intermittent failures | Add synchronization |
| Type coercion | `"1" + 1 = "11"` | Explicit type conversion |
| Async issues | `Promise { <pending> }` | Await/handle promises |

### Investigation Tools

```bash
# Search for error message
grep -r "error message" src/

# Find recent changes
git log --oneline -20
git diff HEAD~5

# Check specific function
grep -r "functionName" src/
```

## Step 4: Fix

Apply the solution:
- Make minimal changes
- Don't refactor while fixing
- One fix per commit

## Step 5: Verify

Confirm the fix:
- [ ] Original issue is resolved
- [ ] No new issues introduced
- [ ] Tests pass
- [ ] Manual verification done

## Output Format

```markdown
## Debug Report

### Issue
[Description of the bug]

### Reproduction Steps
1. Step one
2. Step two
3. Observe error

### Root Cause
[Explanation of why this happens]

### Location
- **File**: `src/utils/parser.ts`
- **Line**: 45-52
- **Function**: `parseInput()`

### Fix Applied
[Description of the fix]

### Verification
- [x] Issue resolved
- [x] Tests pass
- [x] No regression
```