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.
Wann einsetzen: A specific input causes a panic and you can't see where without a debugger.
Voraussetzungen
Server/skill installed and authenticated — See repo README
Ablauf
Reproduce under debugger
Using the debug skill, run main_test.go::TestPanicCase under delve with a breakpoint at the panic frame.✓ Kopiert
→ Process paused at the panic
Inspect
Print locals and the call chain. Show me which variable is nil.✓ Kopiert
→ Variable value + caller chain
Ergebnis: Bug located, not guessed.
Fallstricke
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.
Kosten & Limits
Was der Betrieb kostet
API-Kontingent
See provider docs for rate limits
Tokens pro Aufruf
Varies by tool
Kosten in €
See repo README for pricing details
Tipp
Cache tool results and avoid repeated identical calls.
Sicherheit
Rechte, Secrets, Reichweite
Credential-Speicherung: Use environment variables; never commit secrets
Datenabfluss: Tool calls go to the provider's API as documented
Fehlerbehebung
Häufige Fehler und Lösungen
delve not found
Install delve: go install github.com/go-delve/delve/cmd/dlv@latest.
Prüfen: dlv version
debugger detaches randomly
Long pauses can hit the IDE's heartbeat. Use the skill's --no-heartbeat option for slow flows.