debugging-code
Interactively debug source code — set breakpoints, step through execution line by line, inspect live variable state, evaluate expressions against the running program, and navigate the call stack to trace root causes. Use when a program crashes, raises unexpected exceptions, produces...
Profile →npx skills add sickn33/agentic-awesome-skills --skill debugging-code --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Interactive Debugger ## When to Use Use this skill when you need interactively debug source code — set breakpoints, step through execution line by line, inspect live variable state, evaluate expressions against the running program, and navigate the call stack to trace root causes. Use when a program crashes, raises unexpected exceptions, produces... Use when a program crashes, produces wrong output, or you need to understand exactly how execution reached a particular state — and running it again with more print statements won't give you the answer fast enough. You can pause a running program at any point, read live variable values and the call stack at that exact moment, step forward line by line or jump to the next breakpoint, and evaluate arbitrary expressions against the live process — all without restarting. ## Setup This skill uses `dap`, a CLI tool that background daemon to interact with the debugger via the DAP Protocol, maintain the debugger state, so you can simply interact with it with multiple calls. If `dap` isn't installed (check: `command -v dap`), install it NOW. Ask/notify the user before proceeding to install it. From Homebrew (macOS) ```bash brew install AlmogBa
- When to Use
- Setup
- Starting a Session
- The Debugging Mindset
- Know Your State
- Forming a Hypothesis
- Setting Breakpoints Strategically
- Managing Breakpoints Mid-Session
- Conditional Breakpoints
- Invariant Breakpoints
- Navigating Execution
- Skipping Ahead
- Advanced Scenarios
- Walkthrough
brew install AlmogBaku/tap/dap bash scripts/install-dap.sh go install github.com/AlmogBaku/debug-skill/cmd/dap@latest dap continue --break app.py:50 # add breakpoint deeper, then continue dap continue --remove-break app.py:20 # drop a breakpoint you're done with dap break add app.py:42 app.py:60 # add multiple breakpoints at once dap break list # see what's set dap break clear # start fresh dap debug app.py --break "app.py:42:i == 100" # skip 99 iterations, stop on the one that matters dap debug app.py --break "app.py:30:user_id == 123" # reproduce a user-specific bug
What does the debugging-code skill do?
Interactively debug source code — set breakpoints, step through execution line by line, inspect live variable state, evaluate expressions against the running program, and navigate the call stack to trace root causes. Use when a program crashes, raises unexpected exceptions, produces...
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill debugging-code --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.