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 wrong output, when you need to understand how execution reached a certain state, or when print-statement debugging isn't revealing enough.

Try your first task

Investigate a runtime bug with live state

Start a fresh conversation.

Use the debugging-code skill to investigate why <program-path> produces <unexpected output or exception>. Reproduce it with <arguments or test case>, pause near <file:line>, inspect the live local variables and call stack, step through the smallest relevant execution path, and evaluate <expression> if useful. Report the likely root cause and the observed evidence without modifying any files.

Required inputs

An installed dap CLI
A compatible language-specific debug adapter
Program path, such as <program-path>
Bug symptom or exception
Reproduction arguments or test case
A useful breakpoint location, such as <file:line>
Optional expression to evaluate

Suggested template by Skill Leaderboard, grounded in the linked source. Task evidence ↗

Inside SKILL.md

268 lines

Section content has not been verified for this skill yet.

Full source remains withheld under the current source-display policy. Read the author’s source ↗