debugger

To systematically troubleshoot a software issue, the debugger skill isolates potential causes across layers like network, process, config, dependencies, data, and code. It reproduces the issue to determine the root cause and proposes a structured fix plan with clear verification steps.

The best way to reproduce a bug for evidence-based diagnosis is to gather user-reported symptoms and systematically triage the intent. By isolating layers and testing hypotheses with minimal changes, you can reliably reproduce the issue and document the findings.

To diagnose whether a failure stems from network, config, or code dependencies, you systematically isolate each layer to reproduce the issue. Structured triage identifies the root cause through evidence-based steps, testing hypotheses across layers before applying a fix.

Yes, you can use structured debugging to propose a fix plan with verification steps. After systematically isolating layers and reproducing the issue to find the root cause, the process outputs a documented fix plan with clear verification steps and rationale for future reference.

You should document the rationale and outcome of a root-cause analysis to provide evidence-based diagnosis records for future reference. Documenting reproducible symptoms, isolated layers, and the final fix rationale ensures structured triage outcomes are preserved for subsequent troubleshooting.

When initial bug reproduction steps fail to isolate the root cause, systematically expand your triage across remaining layers like network, process, config, dependencies, data, and code. Gather more symptoms, test new hypotheses with minimal changes, and document findings to pinpoint the issue.