systematic-debugging

Guide four-phase debugging from root cause investigation to verified fixes.

Updated Jan 9, 2026

Search Tags:#testing #debugging #troubleshooting #software development #root cause analysis #bug fixing

Ready to run

npx skills add https://github.com/maplin-co/ai-course --skill systematic-debugging-maplin-co

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/maplin-co/ai-course/tree/main/.opencode/skill/systematic-debugging
Command: npx skills add https://github.com/maplin-co/ai-course --skill systematic-debugging-maplin-co

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents wasted time and new bugs by enforcing a structured, four-phase framework for debugging, ensuring root cause analysis before any fixes are attempted.

Core Features & Use Cases

Root Cause Investigation: Systematically gather evidence, reproduce issues, and trace data flow.
Pattern Analysis: Identify similarities in working code and understand dependencies.
Hypothesis Testing: Formulate and test single, minimal hypotheses.
Implementation: Create failing tests and implement single, verified fixes.
Use Case: When a critical test fails in CI, instead of guessing, use this Skill to meticulously investigate the error messages, check recent changes, and trace the data flow to pinpoint the exact source of the failure before proposing any code modifications.

Quick Start

Use the systematic-debugging skill to investigate the root cause of the latest test failure.

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 a bug instead of just patching symptoms?▼

Systematic debugging enforces root cause investigation by guiding you through evidence gathering, reproduction, data flow tracing, and pattern analysis before attempting fixes. It formulates and tests single, minimal hypotheses to pinpoint exact failure sources.

What is the best way to debug a critical CI test failure without guessing?▼

Debug a CI test failure by meticulously investigating error messages, checking recent changes, and tracing data flow to pinpoint the exact source before proposing modifications. This prevents wasted time and avoids introducing new bugs.

How do I systematically troubleshoot unexpected software behavior?▼

Troubleshoot unexpected behavior using a four-phase framework: investigate root causes by gathering evidence, analyze patterns in working code, test single minimal hypotheses, and implement verified fixes with failing tests to prevent recurring issues.

Does systematic debugging work with test-driven development practices?▼

Yes, systematic debugging integrates with test-driven development by creating failing tests during the implementation phase. This approach ensures single, verified fixes address the exact root cause identified during hypothesis testing.

What are the limitations of fixing bugs without a structured root cause analysis?▼

Fixing bugs without structured root cause analysis leads to wasted time and introduces new bugs. Skipping evidence gathering, pattern analysis, and hypothesis testing risks patching symptoms rather than resolving the exact failure source.

How do I create minimal hypotheses when fixing software bugs?▼

Create minimal hypotheses by formulating and testing a single assumption at a time based on gathered evidence and pattern analysis. This structured approach ensures you verify the exact failure source before implementing code modifications.