debugging-code

Enables interactive debugging of source code via Debug Adapter Protocol (DAP) CLI tool.

312|26|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/AlmogBaku/debug-skill --skill debugging-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging-code
Source: https://github.com/AlmogBaku/debug-skill/tree/main/skills/debugging-code
Command: npx skills add https://github.com/AlmogBaku/debug-skill --skill debugging-code

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill empowers AI coding agents to debug source code interactively, moving beyond print statements to utilize a full-fledged debugger.

Core Features & Use Cases

  • Interactive Debugging: Set breakpoints, step through code execution line-by-line, inspect live variable states, evaluate expressions, and navigate the call stack.
  • Root Cause Analysis: Ideal for diagnosing crashes, unexpected exceptions, incorrect output, or understanding complex execution flows.
  • Use Case: When a Python script fails with an unhandled exception, use this Skill to set a breakpoint just before the suspected error, inspect the variables, and trace the execution path to pinpoint the exact cause.

Quick Start

Use the debugging-code skill to debug the file 'main.py' and set a breakpoint at line 50.

Frequently Asked Questions about debugging-code

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug source code interactively instead of using print statements?

Interactive debugging allows you to set breakpoints, step through code execution line-by-line, inspect live variable states, and navigate the call stack to identify root causes. This approach replaces print statements with a full-fledged debugger to pinpoint exact failure points.

Does interactive debugging work with Python, Go, and TypeScript code?

Interactive debugging supports Python, Go, and TypeScript code via the Debug Adapter Protocol (DAP). The 'dap' CLI tool facilitates cross-language debugging by enabling expression evaluation and call stack analysis across these supported programming languages.

How do I diagnose a crash or unhandled exception using a debugger?

To diagnose a crash or unhandled exception, set a breakpoint just before the suspected error, inspect the variables, and trace the execution path. This root cause analysis isolates the exact state and code execution flow triggering the failure.

What is the best way to trace complex execution flows and inspect variables in source code?

The best way to trace complex execution flows is by setting breakpoints and stepping through execution line-by-line. You can inspect live variable states, evaluate expressions, and analyze the call stack to understand intricate execution paths and resolve bugs.

Can I evaluate expressions and analyze the call stack during code execution?

Yes, you can evaluate expressions and analyze the call stack during code execution. Interactive debugging via the Debug Adapter Protocol enables real-time variable inspection and expression evaluation to diagnose unexpected output or incorrect behavior.

Do I need the Debug Adapter Protocol CLI tool to set breakpoints in source code?

Yes, the 'dap' CLI tool is required to set breakpoints and perform interactive debugging across supported languages. It acts as the interface for the Debug Adapter Protocol, enabling step-through execution and variable inspection within your code.