Claude-code-customes debug-error

Advanced debugging system with Serena MCP integration for intelligent codebase analysis and error resolution

install

source · Clone the upstream repo

git clone https://github.com/sc30gsw/claude-code-customes

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/sc30gsw/claude-code-customes "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.claude/skills/debug-error" ~/.claude/skills/sc30gsw-claude-code-customes-debug-error && rm -rf "$T"

manifest: .claude/skills/debug-error/SKILL.md

source content

Debug Error

Systematic debugging with Serena MCP for smart codebase analysis and efficient error resolution.

Usage

/debug-error "<error_description>" [options]

Options

Option	Description	Example
`--analyze` , `-a`	Enable deep Serena analysis	`/debug-error "crash" -a`
`--trace` , `-t`	Code flow tracing	`/debug-error "logic error" -t`
`--serena-deep` , `-s`	Full Serena toolkit usage	`/debug-error "complex bug" -s`
`--pattern-search` , `-p`	Find similar error patterns	`/debug-error "timeout" -p`
`--memory` , `-m`	Use debugging memory	`/debug-error "recurring issue" -m`
`--interactive` , `-i`	Step-by-step guidance	`/debug-error "unknown issue" -i`
`--implement`	Implement fix automatically	`/debug-error "known solution" --implement`

Tool Priorities

ALWAYS prioritize mcp__serena__ tools when available:

Error Analysis (Serena MCP First)

Pattern Search: Use
```
mcp__serena__search_for_pattern
```
to find error patterns
Symbol Analysis: Use
```
mcp__serena__find_symbol
```
for error location context
Reference Tracking: Use
```
mcp__serena__find_referencing_symbols
```
to trace propagation

Memory & Learning

Previous Solutions: Use
```
mcp__serena__read_memory
```
to recall similar sessions
Pattern Storage: Use
```
mcp__serena__write_memory
```
to store approaches

Workflow

Error Information Gathering
- Collect error message, stack trace, and error code
- Note timing, location, and frequency
- Use
```
mcp__serena__search_for_pattern
```
  to find related patterns
Reproduce the Error
- Create minimal test case
- Document exact steps
Stack Trace Analysis
- Read from bottom to top
- Identify exact failing line
- Trace execution path
Code Context Investigation
- Use
```
mcp__serena__find_symbol
```
  for location context
- Use
```
mcp__serena__find_referencing_symbols
```
  for dependencies
- Check git history and recent modifications
Hypothesis Formation
- Consider common causes: null references, type mismatches, race conditions
Systematic Investigation
- Use Serena for intelligent testing
- Use
```
mcp__serena__insert_after_symbol
```
  for targeted logging
Solution Implementation
- Use
```
mcp__serena__replace_symbol_body
```
  for targeted fixes
- Add comprehensive error handling
Testing and Prevention
- Test fix against original error
- Add unit and integration tests
- Improve error handling and logging

Best Practices

Start with Pattern Search: Always check for similar issues first
Use Memory: Leverage past debugging sessions
Trace Dependencies: Understand error propagation
Document Solutions: Store successful approaches for future reference