systematic-debugging

Guide engineers through a four-phase debugging workflow to identify root causes.

27|5|Updated Apr 3, 2026

Search Tags:#debugging #troubleshooting #systematic #quality-assurance #phases #root-cause-analysis

Ready to run

npx skills add https://github.com/Fandry96/k3-agentic-skills --skill systematic-debugging-fandry96

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/Fandry96/k3-agentic-skills/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/Fandry96/k3-agentic-skills --skill systematic-debugging-fandry96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Random fixes waste time and create new bugs. A disciplined, four-phase approach ensures root cause is identified before any fixes are proposed, reducing rework and improving reliability.

Core Features & Use Cases

Four-phase debugging workflow: Phase 1 Root Cause Investigation, Phase 2 Pattern Analysis, Phase 3 Hypothesis & Testing, Phase 4 Implementation.
Strong evidence gathering and reproducibility checks to trace data flow and verify findings.
Red flags and quick reference guidance to avoid shortcuts and maintain process discipline.
Supporting techniques and references to help diagnose complex multi-component systems.

Quick Start

Apply this skill to a failing system to begin Phase 1 root-cause investigation and guide the full debugging workflow.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I systematically debug a failing test or production issue?▼

Systematically debug a failing test by following a four-phase workflow: root cause investigation, pattern analysis, hypothesis testing, and implementation. This enforces evidence gathering and reproducibility checks before applying any fixes.

What is the best way to find the root cause of a bug before applying fixes?▼

The best way to find a root cause is through pattern analysis and evidence gathering. By tracing data flow and verifying reproducibility, you identify the true source of the bug before implementation, reducing rework.

How do I troubleshoot performance regressions in multi-component systems?▼

Troubleshoot performance regressions in multi-component systems using root-cause debugging. This applies supporting techniques to diagnose complex interactions, ensuring you verify findings with controlled testing.

Why does random fixing waste time and create new bugs?▼

Random fixing wastes time and creates new bugs because it skips root cause investigation. A disciplined debugging approach mandates hypothesis testing and controlled testing before implementation to prevent introducing new issues.

Can I use root-cause analysis for integration bugs across software projects?▼

Yes, you can use root-cause analysis for integration bugs across software projects. The debugging workflow applies to test failures, production issues, and performance regressions, ensuring process discipline.

What are the limitations of systematic debugging for complex systems?▼

Systematic debugging for complex systems requires strict adherence to a four-phase workflow and can be slowed by the need for strong evidence gathering, reproducibility checks, and controlled testing before implementation.