skills.rest
xiaohei-info
xiaohei-infoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Enforce a four-phase debugging workflow for software issues.

28|2|Updated May 4, 2026
Search Tags:#testing#debugging#investigation#troubleshooting#root-cause#software-engineering
One-click install
npx skills add https://github.com/xiaohei-info/oh-my-agent-skills --skill systematic-debugging-xiaohei-info
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/xiaohei-info/oh-my-agent-skills/tree/main/skills/engineering-execution/systematic-debugging
Command: npx skills add https://github.com/xiaohei-info/oh-my-agent-skills --skill systematic-debugging-xiaohei-info

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the common failure of applying superficial patches to symptoms, which often leads to new bugs and wasted time, by enforcing a rigorous investigation before any code changes are made.

Core Features & Use Cases

  • Root Cause Investigation: Provides a structured framework to trace data flow, analyze error messages, and isolate the specific component causing the failure.
  • Scientific Hypothesis Testing: Guides the user to form specific, testable theories and verify them with minimal, isolated changes.
  • Architectural Guardrails: Includes a "Rule of Three" to identify when a bug is actually an architectural flaw, preventing endless cycles of ineffective patching.

Quick Start

Use the systematic-debugging skill to investigate the failing test in the current module by following the four-phase process.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is a root cause investigation process for software bugs?▼

Root cause investigation is a structured debugging workflow that traces data flow and analyzes error messages to isolate the exact component causing a failure before any code changes are made. It prevents superficial patches that introduce regressions.

How do I debug a failing test without introducing new bugs?▼

To debug a failing test safely, follow a four-phase process: investigate the failure, analyze patterns, test hypotheses with minimal isolated changes, and implement the fix. This ensures reliable, regression-free resolutions.

What is the best way to troubleshoot complex production bugs?▼

The best way to troubleshoot complex production bugs is to enforce a scientific hypothesis testing approach. Form specific, testable theories about the failure and verify them to ensure you are fixing the actual issue.

When should I stop patching and fix the architecture during debugging?▼

You should stop patching and fix the architecture when a bug hits the "Rule of Three," which identifies repeated failures as an architectural flaw rather than an isolated bug, preventing endless cycles of ineffective patching.

Do I need terminal and file-search tools to investigate system performance issues?▼

Yes, you need terminal and file-search tools to investigate system performance issues. The debugging process requires integration with these tools to effectively trace data flow and isolate the failing component.

Related Skills

Explore More Software Engineering Skills→
derHakenderHaken
437

systematic-debugging

Trace data flow and apply a four-phase process to fix root causes.

Community
Advanced
ishandutta2007ishandutta2007
13

Systematic Debugging

Diagnose software failures through reproduction, hypothesis testing, and regression verification.

Community
Advanced
mwaymway
4

systematic-debugging

Identify root causes of bugs and test failures through a four-phase debugging workflow.

Community
Advanced
Donaldshen27Donaldshen27

systematic-debugging

Identify bug root causes through a four-phase systematic debugging framework.

Community
Advanced