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
每次呼叫 Token 數
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.