skills.rest
haJ1t
haJ1tCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Diagnose bugs to verified root cause using reproduce-minimize-hypothesize-bisect-confirm.

Updated May 24, 2026
Search Tags:#debugging#root cause#systematic approach#root cause analysis#bug diagnosis#reproducibility
One-click install
npx skills add https://github.com/haJ1t/senior-dev-squad-skills --skill systematic-debugging-haj1t
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/haJ1t/senior-dev-squad-skills/tree/main/plugins/senior-dev-squad/skills/systematic-debugging
Command: npx skills add https://github.com/haJ1t/senior-dev-squad-skills --skill systematic-debugging-haj1t

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps diagnose and fix bugs by employing a systematic approach, ensuring the root cause is identified before any fix is implemented.

Core Features & Use Cases

  • Reproduce Reliably: Provides a method to reliably reproduce bugs, ensuring the issue can be consistently observed.
  • Minimize Reproduction: Offers steps to create the smallest possible input that triggers the bug, aiding in isolating the problem.
  • Formulate Hypothesis: Guides the user in forming a single, falsifiable hypothesis about the cause of the bug.
  • Test Hypothesis: Instructs on how to test the hypothesis by changing one variable at a time.
  • Bisect the Problem: Uses git bisect to pinpoint the exact commit, line, or layer responsible for the issue.
  • Confirm Root Cause: Encourages documenting the root cause in detail before writing a fix.
  • Verify Fix: Ensures the reproduction script fails on the pre-fix code and passes on the post-fix code.
  • Regression Test and Prevention: Instructs on writing a regression test and adding it to CI to prevent future regressions.

Quick Start

Run the 'systematic-debugging' skill on the reported bug to start the debugging process.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is a systematic approach to debugging and root cause analysis?▼

To debug a flaky bug, first establish reliable reproduction, minimize the input, formulate a falsifiable hypothesis, test one variable at a time, and bisect commits to isolate the exact trigger. This prevents quick fixes from masking deeper issues.

How do I diagnose a bug that resists quick fixes?▼

To debug a bug resisting quick fixes, establish reliable reproduction, minimize the input, formulate a falsifiable hypothesis, test one variable at a time, and bisect commits to isolate the exact trigger. This prevents quick fixes from masking deeper issues.

How do I use git bisect to find a regression?▼

Use git bisect to systematically narrow down commits, testing a single hypothesis at a time to pinpoint the exact code change responsible for the regression. Confirm the root cause by verifying the reproduction script fails before and passes after the fix.

When should I use a scientific method for bug diagnosis?▼

Use a scientific debugging method when a bug resists quick fixes, appears intermittently or flakes, only occurs in one environment, or represents a regression. It ensures you verify the root cause rather than guessing at solutions.

How do I minimize a bug reproduction case to isolate the problem?▼

Minimize bug reproduction by systematically stripping away irrelevant inputs and variables until you create the smallest possible trigger. This isolates the exact conditions causing the failure, making the root cause significantly easier to identify.

Related Skills

Explore More Software Engineering Skills→
buiducnhatbuiducnhat
52

fix

Diagnose software bugs through root-cause analysis and implement verified fixes.

Community
Intermediate
divad12divad12
25

bugfix-tdd

Write a failing regression test before tracing the root cause and fixing the bug.

Community
Intermediate
HouseGarofaloHouseGarofalo
3

git-workflow

Manage advanced Git workflows including rebase, cherry-pick, bisect, and reflog recovery.

Official
Advanced
jayhjenkinsjayhjenkins
1

root-cause-diagnosis

Diagnose metric anomaly root causes using 4-dimension segmentation and hypothesis testing.

Community
Basic