skills.rest
dmulcahey
dmulcaheyCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Trace software bugs to root causes using a four-phase investigation methodology.

Updated Mar 16, 2026
Search Tags:#debugging#troubleshooting#defense-in-depth#systematic#process#root-cause
One-click install
npx skills add https://github.com/dmulcahey/featureforge --skill systematic-debugging-dmulcahey
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/dmulcahey/featureforge/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/dmulcahey/featureforge --skill systematic-debugging-dmulcahey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging provides a structured, repeatable approach to diagnosing bugs by focusing on root causes rather than symptoms, reducing time to resolution and preventing regressions.

Core Features & Use Cases

  • Four-phase methodology: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation.
  • Anti-patterns and Redundancy: explicit guidance to avoid rushing, shortcuts, and symptom fixes.
  • Defense-in-depth: multi-layer validation and instrumentation to catch issues across layers.
  • Testing and validation support: recommended alignment with test-driven development and real-world incident handling.
  • Related skills: root-cause tracing, defense-in-depth, and condition-based waiting patterns for robust debugging workflows.

Quick Start

Load the skill and begin with Phase 1, then progress through Phase 2, Phase 3, and Phase 4 to resolve the issue.

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 how does it find root causes?▼

Systematic debugging is a structured methodology that traces bugs to their root causes rather than applying symptomatic patches. It uses a four-phase investigation process to reduce time to resolution and prevent future regressions across codebases.

How do I debug flaky tests and production incidents systematically?▼

Debug flaky tests and production incidents by progressing through four phases: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation. This enforces structured troubleshooting to resolve the actual fault instead of masking symptoms.

What's the best way to stop recurring software bugs and prevent regressions?▼

The best way to stop recurring software bugs is applying defense-in-depth during debugging. This uses multi-layer validation and instrumentation across system layers to catch issues and ensure systematic fixes prevent regression.

Can I use this systematic troubleshooting process for any codebase?▼

Yes, this systematic troubleshooting process applies to software bugs, flaky tests, and production incidents across any codebase. It requires no specific dependencies, making it adaptable to diverse development environments.

Why does rushing to patch symptoms fail during root cause investigation?▼

Rushing to patch symptoms fails because it skips the root cause investigation phase. Systematic debugging explicitly avoids shortcuts and symptom fixes, requiring thorough pattern analysis and hypothesis testing before implementation to prevent regressions.

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

Yes, systematic debugging aligns with test-driven development workflows. It supports testing and validation by enforcing phase-based investigation and hypothesis testing, ensuring real-world incident handling is verified before applying fixes.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
SkogAISkogAI
1

systematic-debugging

Investigate root causes before implementing fixes for software bugs.

Official
Basic
hoanghd218hoanghd218

debug

Trace bugs to root causes using systematic debugging phases and validation.

Community
Advanced
AmidVoshakulAmidVoshakul

incident-responder

Structure incident response with severity classification, communication protocols, and recovery procedures.

Community
Advanced