systematic-debugging

Guide hypothesis-driven root-cause analysis for debugging software issues.

10|4|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/sbknana/equipa --skill systematic-debugging-sbknana
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/sbknana/equipa/tree/main/skills/debugger/skills/systematic-debugging
Command: npx skills add https://github.com/sbknana/equipa --skill systematic-debugging-sbknana

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging helps engineers quickly identify and fix root causes rather than masking symptoms by guiding a disciplined, hypothesis-driven process.

Core Features & Use Cases

  • Reproduction and characterization: define exact symptom, context, and reproduce steps to isolate the issue.
  • Hypothesis-driven analysis: generate testable root-cause hypotheses and prioritize by likelihood.
  • Binary search for root cause: iteratively validate hypotheses by checking inputs, data flow, and decision points to converge on the fault.
  • Verification and guardrails: confirm fixes with regression checks and maintain documentation of observed behavior and decisions.

Quick Start

Run Step 1 to reproduce and characterize the bug, then proceed to Step 2 to form testable hypotheses.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is hypothesis-driven root-cause analysis for debugging?

Hypothesis-driven root-cause analysis is a systematic debugging method that generates testable root-cause hypotheses and prioritizes them by likelihood. It converges on the exact fault using binary search rather than masking symptoms.

How do I debug a failing test or runtime regression systematically?

To debug a failing test or runtime regression systematically, start by reproducing and characterizing the exact symptom. Formulate testable hypotheses, then iteratively validate inputs and decision points using binary search to converge on the fault.

When do I need a structured debugging workflow for bug reports?

You need a structured debugging workflow when bug reports require strict reproducibility and surgical fixes to prevent recurring symptoms. It enforces hypothesis testing and verification with regression checks to ensure the root cause is eliminated.

Does systematic debugging work for complex software regressions?

Systematic debugging works for complex software regressions by applying binary search across inputs, data flow, and decision points. It guides engineers through iterative hypothesis validation to pinpoint the exact code fault regardless of complexity.

What is the best way to isolate a root cause from runtime errors?

The best way to isolate root causes from runtime errors is combining structured log analysis with binary search. This method validates prioritized hypotheses against observed behavior and data flow to surgically locate the fault.

How do I verify a surgical fix after root-cause analysis?

Verify a surgical fix after root-cause analysis by running regression checks and confirming the original reproduction steps no longer fail. Documenting observed behavior and decisions maintains guardrails against future regressions.