Skills Guide

DAP Debugging

VerifiedSafe

Use VS Code debugger (DAP) to set breakpoints, step through code, and inspect runtime state.

Download and use
Sby Skills Guide Bot
DevelopmentIntermediate
7/25/2026
Claude Code
#debug#dap#runtime#breakpoints#vscode

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Automated summary

Uses the VS Code debugger (DAP) to set breakpoints, step through code, and inspect runtime state.

Strengths

  • LSP-informed breakpoint placement for accurate debugging
  • One-command smart debug with auto-fix and analysis
  • Supports custom expression evaluation during debugging
  • Multiple stepping modes for fine-grained control

Limitations

  • Requires VS Code debugger to be configured and running
  • Only works with languages supported by DAP
  • Bridge commands may not be available on all systems
When to use it

When you need to understand runtime behavior, trace actual execution paths, or inspect variable values dynamically.

When not to use it

For static type errors or syntax bugs; use LSP diagnostics and linting instead.

Security analysis

Safe
Quality score85/100

The skill only uses predefined debugging commands (bridge-smart-debug, bridge-inspect, bridge-recon) which are restricted to setting breakpoints, launching programs, and inspecting variables; no arbitrary shell execution, network exfiltration, or destructive actions are possible. The skill does not execute untrusted input beyond the expression evaluation in a debugger sandbox, which is standard and safe in this context.

No concerns found

How this analysis is made

Examples

Smart debug a specific symbol
Debug the function findUser in app.js to see where it fails.
Manual breakpoint at a line
Set a breakpoint at line 15 of app.js and inspect the user variable.
Step through code using MCP tools
Step over the next line of code and show me all local variables.

name: dap-debug description: Use VS Code debugger (DAP) to set breakpoints, step through code, and inspect runtime state. Invoke when you need to understand runtime behavior, not just static types. user_invocable: true allowed-tools: Bash(bridge-smart-debug *), Bash(bridge-inspect *), Bash(bridge-recon *)

Debug

Smart debug (preferred — LSP-informed)

One command: auto-fix → LSP recon → analyze → set breakpoints at suspicious lines → launch → dump variables at each hit → stop.

# With a symbol to focus on (best results)
bridge-smart-debug <type> <program> <file> <symbol>

# Without a symbol (breaks at diagnostic errors or first function)
bridge-smart-debug <type> <program> <file>

# With expression evaluation
bridge-smart-debug node app.js app.js findUser --eval "typeof user" --eval "users.length"

The script automatically decides WHERE to break based on LSP analysis:

  • Lines with type errors from diagnostics
  • Callers that invoke the target symbol (where bad data originates)
  • Reference sites of the symbol
  • The symbol's definition
  • Falls back to first function if nothing else found

Manual inspect (when you know the exact line)

bridge-inspect <type> <program> <file> <line>
bridge-inspect node app.js app.js 15 --condition "user === undefined" --eval "users.length"

For interactive stepping, use MCP tools directly

When you need to step through code line by line, fetch DAP tools via ToolSearch:

  • mcp__vscode-bridge__debugSetBreakpoints + debugStart + debugWaitForEvent
  • mcp__vscode-bridge__debugStepOver / debugStepInto / debugStepOut
  • mcp__vscode-bridge__debugGetVariables + debugEvaluate
  • mcp__vscode-bridge__debugContinue + debugStop

When to use debug (not just LSP)

  • Bug depends on runtime data (what value a variable actually has)
  • Dynamic language where static types aren't available
  • Need to trace actual execution path
  • Want to inspect state without modifying code

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/dap-debugging-mrzxup07/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/dap-debugging-mrzxup07' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/dap-debugging-mrzxup07/download' --output '.skill-downloads/dap-debugging-mrzxup07/SKILL.md.part' && mv '.skill-downloads/dap-debugging-mrzxup07/SKILL.md.part' '.skill-downloads/dap-debugging-mrzxup07/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash(bridge-smart-debug *), Bash(bridge-inspect *), Bash(bridge-recon *)

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/dap-debugging-mrzxup07/SKILL.md' && test -s '.skill-downloads/dap-debugging-mrzxup07/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/dap-debug' && cp -R '.skill-downloads/dap-debugging-mrzxup07' '.claude/skills/dap-debug'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/dap-debugging-mrzxup07'

openskills read 'dap-debugging-mrzxup07'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/dap-debugging-mrzxup07/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot