Systematic Debugging

What it does

Systematic Debugging provides a structured four-phase protocol that helps engineers and agent workers find the root cause before applying fixes. The skill emphasizes reproducible tests, investigation techniques (stack traces, data flow, bisecting, reference comparisons), hypothesis formation with prediction tests, and minimal, test-backed fixes. It prevents repeated guesswork and reduces time-to-resolution.

When to use it

Invoke this skill whenever a test fails, an unexpected error appears, or a bug report arrives. It’s recommended under time pressure to avoid wasteful guess-and-check cycles and when you need repeatable evidence for fixes and regression checks.

What's included

• Scripts: None bundled (has_scripts=false)
• References: None bundled (has_references=false)
• Instructions: A detailed four-phase workflow with gates at each phase, constraints (one fix at a time, no changes until root cause hypothesis), red flags, and success indicators to ensure disciplined debugging.

Compatible agents

Useful for general developer-assistant agents, CI-driven debugging flows, and any agent that performs code changes or test runs (Copilot-style assistants, CI bots, and developer-facing automation).