Debug Session Analysis

ProductivityBeginner

Claude Code's official bundled skill /debug analyzes debug logs from current or past sessions to diagnose problems. It automatically detects error patterns, failed tool calls, abnormal token usage, and presents root causes with recommended fixes.

Trigger/debug

FrequencyWhen issues occur

When Claude Code behaves unexpectedly? Run /debug to analyze session logs and identify root cause

When token usage is abnormally high? Use /debug to find which tool calls consumed the most tokens

DebugTroubleshootingBundled SkillSession

How It Works

Run /debug → Collect session logs

↓

Phase 1: 2 analyses in parallel

error-scan

Error pattern and failure detection

usage-analysis

Token/tool usage analysis

↓

Diagnose issues + Suggest fixes

↓

✓ Diagnostic report + Recommended actions

Skill Code

# Debug Session — Built-in Bundled Skill
## Trigger: /debug

Claude Code's official bundled skill for session troubleshooting.

### What it analyzes:

1. Error patterns:
  - Failed tool calls and their causes
  - Permission denials and sandbox issues
  - Network/API errors

2. Performance issues:
  - Unusually high token consumption
  - Slow tool executions
  - Repeated retry patterns

3. Behavioral anomalies:
  - Unexpected model responses
  - Context window overflow signals
  - Tool selection mismatches

### Usage:
```bash
# Debug current session
/debug

# Debug a specific past session
/debug --session <session-id>

# Debug with verbose output
/debug --verbose
```

### Output:
- Issue summary with severity levels
- Root cause analysis
- Recommended fixes or workarounds
- Links to relevant documentation

Copy and paste into your CLAUDE.md to start using immediately.

How Debug Session Analysis Works

Debug collects session logs and analyzes error patterns, failed tool calls, and abnormal token consumption. It classifies issues by severity and provides root cause analysis with recommended fixes.