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
One-liner. Verify with claude mcp list. Remove with claude mcp remove.
Use Cases
Real-world ways to use Debug Skill
Find the nil deref a print loop can't catch
👤 Backend devs⏱ ~15 minintermediate
When to use: A specific input causes a panic and you can't see where without a debugger.
Prerequisites
Server/skill installed and authenticated — See repo README
Flow
Reproduce under debugger
Using the debug skill, run main_test.go::TestPanicCase under delve with a breakpoint at the panic frame.✓ Copied
→ Process paused at the panic
Inspect
Print locals and the call chain. Show me which variable is nil.✓ Copied
→ Variable value + caller chain
Outcome: Bug located, not guessed.
Pitfalls
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.
Cost & Limits
What this costs to run
API quota
See provider docs for rate limits
Tokens per call
Varies by tool
Monetary
See repo README for pricing details
Tip
Cache tool results and avoid repeated identical calls.
Security
Permissions, secrets, blast radius
Credential storage: Use environment variables; never commit secrets
Data egress: Tool calls go to the provider's API as documented
Troubleshooting
Common errors and fixes
delve not found
Install delve: go install github.com/go-delve/delve/cmd/dlv@latest.
Verify: dlv version
debugger detaches randomly
Long pauses can hit the IDE's heartbeat. Use the skill's --no-heartbeat option for slow flows.