Automated Instrumented Debugging

Core Philosophy: Don't guess. Instrument, measure, and let the data reveal the root cause.

Overview

This skill empowers you to debug complex issues by systematically injecting lightweight probes (fetch calls) into the codebase. These probes stream real-time execution data (function entries, variable states, errors) to a local debug server, allowing you to reconstruct the exact execution flow without relying on scattered console logs or interactive debuggers.

When to Use

• Complexity: The bug involves data flow across 3+ functions or asynchronous chains.
• Invisibility: Code runs in blind environments (Docker, CI, remote servers).
• Persistency: You need to analyze the chronology of events post-execution.
• Systematic Analysis: You need hard evidence to prove a hypothesis.

Systematic Debugging Process

Follow this 4-phase loop to resolve issues efficiently.