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.
claude mcp add debug-skill -- git clone https://github.com/AlmogBaku/debug-skill ~/.claude/skills/debug-skill
ワンライナー。claude mcp list で確認、claude mcp remove で削除。
ユースケース
実用的な使い方: Debug Skill
Find the nil deref a print loop can't catch
👤 Backend devs⏱ ~15 minintermediate
使うタイミング: A specific input causes a panic and you can't see where without a debugger.
前提条件
Server/skill installed and authenticated — See repo README
フロー
Reproduce under debugger
Using the debug skill, run main_test.go::TestPanicCase under delve with a breakpoint at the panic frame.✓ コピーしました
→ Process paused at the panic
Inspect
Print locals and the call chain. Show me which variable is nil.✓ コピーしました
→ Variable value + caller chain
結果: Bug located, not guessed.
注意点
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.
コストと制限
運用コスト
APIクォータ
See provider docs for rate limits
呼び出しあたりのトークン
Varies by tool
金額
See repo README for pricing details
ヒント
Cache tool results and avoid repeated identical calls.
セキュリティ
権限、シークレット、影響範囲
認証情報の保管: Use environment variables; never commit secrets
データ送信先: Tool calls go to the provider's API as documented
トラブルシューティング
よくあるエラーと対処法
delve not found
Install delve: go install github.com/go-delve/delve/cmd/dlv@latest.
確認: dlv version
debugger detaches randomly
Long pauses can hit the IDE's heartbeat. Use the skill's --no-heartbeat option for slow flows.