npx claudepluginhub almogbaku/debug-skillInteractively debug source code — set breakpoints, step through execution, inspect live variables, evaluate expressions, and trace root causes.
Share bugs, ideas, or general feedback.
Let your coding agent debug like a human developer.
Set breakpoints, step through code, evaluate expressions — the way you actually debug.
If this saves you a debugging session, please star the repo — it helps others find it.
AI coding agents (Claude Code, Codex, Opencode, Cursor) are stuck with print statements and guesswork. debug-skill
gives them what human developers have: a real debugger they can actually use. It ships two things:
dap CLI — a stateless CLI wrapper around
the Debug Adapter Protocol so any agent can drive a real
debugger from BashInstall the skill, and Claude debugs your code the way you would — not with print statements.
The debugging-code skill gives Claude structured knowledge of the debugging workflow: setting breakpoints, stepping
through execution, inspecting locals and the call stack, evaluating expressions mid-run. It uses the dap CLI as its
tool.
Via the plugin marketplace — no manual setup needed:
/plugin marketplace add AlmogBaku/debug-skill
/plugin install debugging-code@debug-skill-marketplace
Via skills.sh — works with Cursor, GitHub Copilot, Windsurf, Cline, and 20+ more agents:
npx skills add AlmogBaku/debug-skill
# or: bunx skills add AlmogBaku/debug-skill
Or manually copy skills/debugging-code/ into your agent's skills.
dap CLIdap wraps the Debug Adapter Protocol behind simple, stateless CLI commands. A background daemon holds the session; the
CLI sends one command and gets back the full context — no interactive terminal required.
# One-liner (Linux & macOS)
bash <(curl -fsSL https://raw.githubusercontent.com/AlmogBaku/debug-skill/master/skills/debugging-code/scripts/install-dap.sh)
From Homebrew (for macOS):
brew install AlmogBaku/tap/dap
From sources:
# Go install
go install github.com/AlmogBaku/debug-skill/cmd/dap@latest
Or download a pre-built binary from the releases page.
dap debug app.py --break app.py:42 # start, stop at breakpoint
dap eval "len(items)" # inspect a value
dap inspect data --depth 2 # expand nested objects
dap step # step over
dap continue # next breakpoint
dap continue --to app.py:50 # run to specific line
dap pause # interrupt if hanging
dap restart # re-run, preserving breakpoint changes
dap stop # end session
Execution commands (debug, continue, step) return full context automatically: current location, surrounding source, local variables, call stack,
and program output. No follow-up calls needed.
# Python
dap debug app.py --break app.py:42
# Go
dap debug main.go --break main.go:15
# Node.js / TypeScript
dap debug server.js --break server.js:10
# Rust / C / C++
dap debug hello.rs --break hello.rs:4
# Attach to a remote debugger (e.g. debugpy in a container)
dap debug --attach container:5678 --backend debugpy --break handler.py:20
# Attach to a running process by PID
dap debug --pid 12345 --backend debugpy