skill_debug

Autonomous debugging in VS Code performs static code analysis to identify risks and plan breakpoints before runtime. It then generates a launch.json configuration and captures runtime telemetry during an iterative debug session to diagnose failures systematically.

Set up an autonomous debug session by opening a VS Code workspace and running the workflow to generate a launch.json. It then guides an iterative debugging loop, capturing raw telemetry and producing an execution timeline to triage failures.

Yes, you can use static analysis to plan breakpoints before runtime in VS Code. The workflow performs static reconnaissance and risk identification to strategically place breakpoints, generating a breakpoint report before executing the code.

Yes, autonomous debugging preserves raw error output and telemetry data. The workflow enforces safe, auditable workflows by capturing raw telemetry and producing an execution timeline alongside the raw error output during the iterative debug session.

You need to generate a launch.json to define the runtime configuration for iterative debugging in VS Code. It enables the workflow to execute the code, capture telemetry, and iterate through the debug session to diagnose failures systematically.

You should avoid using an autonomous debugging workflow if your codebase is not opened in VS Code, as the launch.json generation and breakpoint placement depend on the VS Code environment to execute the iterative debug session.