errors

# Error Pattern Analysis Analyze errors captured from Claude Code sessions to identify patterns and get actionable insights. ## Quick Start ```bash /errors # Batch analysis of historical error patterns /debug # CC 2.1.30 real-time debug for current session ``` ### When to Use Which | Command | Purpose | Scope | |---------|---------|-------| | `/errors` | Batch analysis of error patterns (last 24h/7d) | Historical patterns | | `/debug` | Real-time debug of current session state | Current session | | `/ork:fix-issue` | Full RCA workflow for specific bug | Single issue | > **CC 2.1.169+:** for errors that survive `/clear` and restarts, `claude --safe-mode` boots with every customization disabled (CLAUDE.md/plugins/skills/hooks/MCP) — the one-step test that separates "ork/hook/MCP bug" from "CC bug" before deeper analysis. ## Quick Analysis ```bash # Run batch analysis on last 24h of errors python .claude/scripts/analyze_errors.py # Analyze last 7 days python .claude/scripts/analyze_errors.py --days 7 # Generate markdown report python .claude/scripts/analyze_errors.py --report ``` ## What Gets Captured The error collector hook captures: - Tool name (Bash, mcp__memory__search_nodes, etc.) - Error message (first 500 chars) - Tool input (command/query that failed) - Timestamp and session ID **Location:** `.claude/logs/errors.jsonl` ## Current Error Rules Check learned patterns that trigger warnings: ```bash cat .claude/rules/error_rules.jso...