systematic-debugging

Identify root causes of software defects through a four-phase debugging workflow.

Updated Dec 15, 2025

Search Tags:#root cause #troubleshooting #diagnostics #systematic debugging #software debugging #phased workflow

Ready to run

npx skills add https://github.com/scruffydan/AI-Agents --skill systematic-debugging-scruffydan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/scruffydan/AI-Agents/tree/main/source/skills/systematic-debugging
Command: npx skills add https://github.com/scruffydan/AI-Agents --skill systematic-debugging-scruffydan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined, phase-driven approach to debugging, helping engineers identify root causes instead of applying symptomatic fixes.

Core Features & Use Cases

Phase-driven workflow including Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation.
Guidance on reproducing issues, collecting evidence, comparing against references, and validating fixes.
Useful for test failures, production incidents, and integration problems in multi-component systems.

Quick Start

Reproduce the issue and capture exact error messages and logs.
Gather evidence across all components, check recent changes, and compare with references.
Move through Phases 2-4: analyze patterns, form a hypothesis, test minimally, implement the fix, and verify success.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is a systematic debugging workflow for finding the root cause of software defects?▼

A systematic debugging workflow identifies the root cause of software defects through a four-phase process: root cause investigation, pattern analysis, hypothesis testing, and implementation. It enforces evidence gathering to prevent symptomatic fixes.

How do I debug a production incident in a multi-component system?▼

Debug a production incident by first reproducing the issue and capturing exact error logs. Then gather evidence across all components, check recent changes, compare with references, analyze patterns, and form a hypothesis to test minimally before implementing a fix.

How do I troubleshoot integration issues across multiple components?▼

Troubleshoot integration issues by collecting evidence across all affected components and checking recent changes. Compare behavior against reference implementations, analyze patterns, form a hypothesis, and test it minimally to isolate the root cause before applying a fix.

What is the best way to verify a software fix without applying symptomatic patches?▼

The best way to verify a software fix is to follow a phased workflow: reproduce the issue, gather evidence, form a hypothesis, test it minimally, implement the fix, and validate success. This ensures you address the root cause rather than applying symptomatic patches.

When should I use a phase-driven approach for software debugging?▼

Use a phase-driven approach for software debugging during test failures, production incidents, and integration issues. It is especially useful in multi-component systems where disciplined evidence gathering and pattern analysis are needed to isolate the root cause.

Why do my bug fixes keep regressing when I troubleshoot test failures?▼

Bug fixes regress during troubleshooting when symptomatic patches are applied instead of finding the root cause. A systematic workflow enforces evidence gathering, hypothesis testing, and fix verification to ensure the underlying defect is truly resolved.