systematic-debugging

Systematically debugs issues from root cause investigation to implementation.

14|1|Updated May 24, 2026

Search Tags:#debugging #anti-patterns #root cause #test failures #hypothesis testing #incident response

Ready to run

npx skills add https://github.com/DoraemonHugU/oh-my-harness --skill systematic-debugging-doraemonhugu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/DoraemonHugU/oh-my-harness/tree/main/plugin/skills/systematic-debugging
Command: npx skills add https://github.com/DoraemonHugU/oh-my-harness --skill systematic-debugging-doraemonhugu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents wasted time and new bugs caused by making “quick fixes” without understanding the underlying root cause of an error or unexpected behavior.

Core Features & Use Cases

Root-cause-first debugging (4 phases): Investigation → Pattern analysis → Hypothesis & testing → Implementation, so you always move forward with evidence.
Anti-rationalization guardrails: Explicit rules like “ALWAYS find root cause before attempting fixes” and “DON'T add more fixes on top” after a failed minimal test.
Handles pressure and complexity: Includes guidance for emergencies, multi-component systems, and what to do when you don’t fully understand the issue.

Quick Start

When you see a bug or test failure, read the error messages carefully and complete Phase 1 root cause investigation before proposing any fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I find the root cause of test failures before attempting a fix?▼

To find the root cause of test failures, you must complete a full investigation phase analyzing error messages and behavior patterns before proposing any fixes. This prevents wasted time and new bugs caused by making quick fixes without understanding the underlying issue.

What is the best way to debug multi-component failures when symptoms are misleading?▼

Debugging misleading multi-component failures requires forming a single hypothesis with a minimal test. If the first hypothesis fails, you must stop and re-analyze the root cause rather than adding more fixes on top of failed attempts.

How do I handle incident response debugging under time pressure without taking shortcuts?▼

Incident response debugging under time pressure still requires completing Phase 1 root cause investigation before proposing fixes. Anti-rationalization guardrails explicitly enforce finding the root cause first and stopping when a hypothesis fails to prevent compounding errors.

What should I do when my debugging hypothesis fails during a minimal test?▼

When your debugging hypothesis fails during a minimal test, you should stop and re-analyze the root cause. Do not add more fixes on top of the failed attempt, as this violates the systematic debugging process and introduces new bugs.

What are the phases of systematic debugging for unexpected software behavior?▼

Systematic debugging for unexpected behavior involves four phases: Investigation to gather evidence, Pattern analysis to identify trends, Hypothesis and testing to validate a single root cause, and Implementation to apply the fix. You must complete them in order.

When should I avoid quick fixes during local debugging of bug reports?▼

You should avoid quick fixes during local debugging whenever you do not fully understand the issue. Systematic debugging requires finding the root cause first, as making fixes without understanding the underlying behavior causes wasted time and new bugs.