systematic-debugging

Investigate root causes of bugs through four structured debugging phases.

Updated Aug 23, 2026

Search Tags:#testing #debugging #troubleshooting #phases #root-cause #systematic-debugging #debug-process

Ready to run

npx skills add https://github.com/Oxilith/CopilotSkills --skill systematic-debugging-oxilith

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/Oxilith/CopilotSkills/tree/main/.agentskills/skills/systematic-debugging
Command: npx skills add https://github.com/Oxilith/CopilotSkills --skill systematic-debugging-oxilith

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a disciplined, repeatable approach to debugging that helps teams identify the root cause of bugs, test failures, or unexpected behavior before proposing fixes, reducing time wasted on symptom fixes.

Core Features & Use Cases

Structured four-phase process: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation to methodically locate and verify the origin of issues.
Evidence-driven debugging: Emphasizes reproducibility, data flow tracing, and diagnostic instrumentation to prevent guessing.
Broad applicability: Useful for flaky tests, production incidents, performance regressions, and integration failures across software projects.

Quick Start

Document the observed symptom and reproduce the issue.
Proceed through Phase 1–4, collecting evidence and forming testable hypotheses.
Implement the root-cause fix, add a failing test if possible, and re-run to confirm resolution.

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 software and finding root causes?▼

Systematic debugging is a disciplined, four-phase approach to identifying root causes of bugs and unexpected behavior before proposing fixes. It enforces Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation to methodically locate issues.

How do I debug flaky tests and production incidents without guessing?▼

Debug flaky tests and production incidents using evidence-driven debugging that emphasizes reproducibility and data flow tracing. You document observed symptoms, collect diagnostic instrumentation data, and form testable hypotheses across four structured phases to prevent guessing.

What is the best way to troubleshoot test failures and integration failures across software projects?▼

The best way to troubleshoot test failures and integration failures is applying a phased investigation process. It guides you through reproducing the issue, analyzing patterns, testing hypotheses, and implementing verified fixes while minimizing changes and documenting evidence.

How do I fix performance regressions by tracing data flow instead of treating symptoms?▼

Fix performance regressions by tracing data flow through Root Cause Investigation and Pattern Analysis phases. You collect evidence, form hypotheses, and implement the root-cause fix, adding a failing test and re-running to confirm resolution prior to completion.

Does this debugging process work for any technical issue or only specific programming languages?▼

This debugging process applies to any technical issue across software projects, including flaky tests, production incidents, performance regressions, and integration failures. It guides reproduction, data-flow tracing, and phased investigation until a root cause is found.

What are the limitations of phased debugging for urgent production incidents?▼

Phased debugging requires strict adherence to four phases—Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation—demanding evidence collection and documentation. This disciplined approach may delay immediate symptom fixes during urgent production incidents.