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.
Adicione em context_servers. Zed recarrega automaticamente ao salvar.
claude mcp add debug-skill -- git clone https://github.com/AlmogBaku/debug-skill ~/.claude/skills/debug-skill
Uma linha só. Verifique com claude mcp list. Remova com claude mcp remove.
Casos de uso
Usos do mundo real: Debug Skill
Find the nil deref a print loop can't catch
👤 Backend devs⏱ ~15 minintermediate
Quando usar: A specific input causes a panic and you can't see where without a debugger.
Pré-requisitos
Server/skill installed and authenticated — See repo README
Fluxo
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.
Armadilhas
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.
Custo e limites
O que custa rodar
Cota de API
See provider docs for rate limits
Tokens por chamada
Varies by tool
Monetário
See repo README for pricing details
Dica
Cache tool results and avoid repeated identical calls.
Segurança
Permissões, segredos, alcance
Armazenamento de credenciais: Use environment variables; never commit secrets
Saída de dados: Tool calls go to the provider's API as documented
Solução de problemas
Erros comuns e correções
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.