systematic-debugging

Trace root causes through a four-phase debugging workflow.

3|Updated Apr 20, 2026

Search Tags:#debugging #anti-patterns #systematic #phases #root-cause #hypothesis-testing #defense-depth

Ready to run

npx skills add https://github.com/mor-duongmh/morkit-plugin --skill systematic-debugging-mor-duongmh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/mor-duongmh/morkit-plugin/tree/main/plugins/morkit/skills/systematic-debugging
Command: npx skills add https://github.com/mor-duongmh/morkit-plugin --skill systematic-debugging-mor-duongmh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Random fixes waste time and create new bugs. Quick patches mask underlying issues. The core principle is ALWAYS find root cause before attempting fixes. Violating the letter of this process is violating the spirit of debugging.

Core Features & Use Cases

Four-phase structured debugging process (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) with mandatory progression.
Anti-patterns and defensive safeguards to resist shortcuts under pressure.
Effective across bugs, test failures, production issues, flaky tests, and complex systems.

Quick Start

Load the systematic-debugging skill from skills/debugging/systematic-debugging, then follow Phases 1–5 to trace the root cause before proposing fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is systematic debugging and when should I use it?▼

Systematic debugging is a root-cause investigation process that traces bugs instead of applying symptom fixes. Use it for codebase issues, production incidents, QA failures, and flaky tests where random patches waste time or create new bugs.

How do I debug a production incident without applying quick symptom patches?▼

To debug a production incident, follow a four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation. This structured process ensures you gather evidence and confirm the root cause before attempting a guarded fix.

What's the best way to trace the root cause of flaky tests?▼

The best way to trace root causes of flaky tests is through hypothesis testing and pattern analysis. By systematically investigating failures and gathering evidence before implementing fixes, you avoid masking underlying issues with unstable patches.

Can I use this structured debugging method for complex codebase failures?▼

Yes, this structured debugging method works effectively across complex codebases and technical scenarios. It enforces phased progression and includes defensive safeguards to resist shortcuts, ensuring reliable diagnosis even under time-pressured conditions.

Why do my random bug fixes keep creating new issues in my codebase?▼

Random bug fixes create new issues because they mask underlying problems instead of resolving them. You must always find the root cause before attempting fixes; violating this process introduces regression and instability into your system.

Are there limitations to using a phased debugging workflow during time-pressured incidents?▼

A key limitation is the temptation to bypass phases under pressure. The workflow mandates strict progression through investigation, analysis, testing, and implementation, using anti-patterns and defensive safeguards to prevent shortcuts that compromise root-cause discovery.