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.
Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.
claude mcp add debug-skill -- git clone https://github.com/AlmogBaku/debug-skill ~/.claude/skills/debug-skill
Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.
Cas d'usage
Usages concrets : Debug Skill
Find the nil deref a print loop can't catch
👤 Backend devs⏱ ~15 minintermediate
Quand l'utiliser : A specific input causes a panic and you can't see where without a debugger.
Prérequis
Server/skill installed and authenticated — See repo README
Déroulement
Reproduce under debugger
Using the debug skill, run main_test.go::TestPanicCase under delve with a breakpoint at the panic frame.✓ Copié
→ Process paused at the panic
Inspect
Print locals and the call chain. Show me which variable is nil.✓ Copié
→ Variable value + caller chain
Résultat : Bug located, not guessed.
Pièges
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.
Coût et limites
Coût d'exécution
Quota d'API
See provider docs for rate limits
Tokens par appel
Varies by tool
Monétaire
See repo README for pricing details
Astuce
Cache tool results and avoid repeated identical calls.
Sécurité
Permissions, secrets, portée
Stockage des identifiants : Use environment variables; never commit secrets
Sortie de données : Tool calls go to the provider's API as documented
Dépannage
Erreurs courantes et correctifs
delve not found
Install delve: go install github.com/go-delve/delve/cmd/dlv@latest.
Vérifier : dlv version
debugger detaches randomly
Long pauses can hit the IDE's heartbeat. Use the skill's --no-heartbeat option for slow flows.