Loading...
Loading...
Error pattern analysis and troubleshooting for Claude Code sessions. Use when handling errors, fixing failures, troubleshooting issues.
npx skill4agent add yonatangross/orchestkit errors/errors # Batch analysis of historical error patterns
/debug # CC 2.1.30 real-time debug for current session| Command | Purpose | Scope |
|---|---|---|
| Batch analysis of error patterns (last 24h/7d) | Historical patterns |
| Real-time debug of current session state | Current session |
| Full RCA workflow for specific bug | Single issue |
# 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.claude/logs/errors.jsonlcat .claude/rules/error_rules.json | jq '.rules[] | {id, signature, count: .occurrence_count}'| File | Purpose |
|---|---|
| Captures errors to JSONL |
| Warns before risky commands |
| Batch pattern analysis |
| Learned error patterns |
| Raw error log |
pattern: role "X" does not exist
fix: Use Docker connection: docker exec -it orchestkit-postgres-dev psql -U orchestkit_user -d orchestkit_dev
pattern: relation "X" does not exist
fix: Check MCP postgres server connection string - may be connected to wrong databaseanalyze_errors.py.claude/rules/error_rules.json{
"id": "custom-001",
"pattern": "your regex pattern",
"signature": "human readable signature",
"tool": "Bash",
"occurrence_count": 1,
"fix_suggestion": "How to fix this"
}