Most agents 'debug' by printing. This skill actually attaches a debugger (delve, debugpy, gdb) and exposes step/continue/inspect to Claude. Useful for nasty bugs where 'add a log' loops forever.
Añádelo a context_servers. Zed recarga en caliente al guardar.
claude mcp add debug-skill -- git clone https://github.com/AlmogBaku/debug-skill ~/.claude/skills/debug-skill
Un solo comando. Verifica con claude mcp list. Quita con claude mcp remove.
Casos de uso
Usos del mundo real: Debug Skill
Find the nil deref a print loop can't catch
👤 Backend devs⏱ ~15 minintermediate
Cuándo usarlo: A specific input causes a panic and you can't see where without a debugger.
Requisitos previos
Server/skill installed and authenticated — See repo README
Flujo
Reproduce under debugger
Using the debug skill, run main_test.go::TestPanicCase under delve with a breakpoint at the panic frame.✓ Copiado
→ Process paused at the panic
Inspect
Print locals and the call chain. Show me which variable is nil.✓ Copiado
→ Variable value + caller chain
Resultado: Bug located, not guessed.
Errores comunes
Breakpoints by symbol can match multiple methods in Go interfaces — Breakpoints by symbol can match multiple methods in Go interfaces — qualify with the package path.
Coste y límites
Lo que cuesta ejecutarlo
Cuota de API
See provider docs for rate limits
Tokens por llamada
Varies by tool
Monetario
See repo README for pricing details
Consejo
Cache tool results and avoid repeated identical calls.
Seguridad
Permisos, secretos, alcance
Almacenamiento de credenciales: Use environment variables; never commit secrets
Salida de datos: Tool calls go to the provider's API as documented
Resolución de problemas
Errores comunes y soluciones
delve not found
Install delve: go install github.com/go-delve/delve/cmd/dlv@latest.
Verificar: dlv version
debugger detaches randomly
Long pauses can hit the IDE's heartbeat. Use the skill's --no-heartbeat option for slow flows.