systematic-debugging

Automate root-cause analysis across four systematic debugging workflow phases.

Updated Mar 17, 2026

Search Tags:#debugging #troubleshooting #problem-solving #diagnostics #triage #root-cause

Ready to run

npx skills add https://github.com/HemantSudarshan/Dhumichatbot --skill systematic-debugging-hemantsudarshan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/HemantSudarshan/Dhumichatbot/tree/main/skills/06-test/systematic-debugging
Command: npx skills add https://github.com/HemantSudarshan/Dhumichatbot --skill systematic-debugging-hemantsudarshan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Random debugging efforts waste time and mask root causes. Systematic debugging enforces root-cause investigation before proposing fixes to reduce toil and rework.

Core Features & Use Cases

Phase 1: Root Cause Investigation — read error messages, reproduce reliably, inspect recent changes, and collect evidence.
Phase 2: Pattern Analysis — identify working analogs, compare with references, and surface differences.
Phase 3: Hypothesis and Testing — formulate a single hypothesis, test minimally, verify results.
Phase 4: Implementation — create a failing test, implement the fix, verify, and validate regression risk.
Supporting techniques: root-cause-tracing.md, defense-in-depth.md, condition-based-waiting.md.

Quick Start

Begin Phase 1 by carefully reading errors, reproducing the issue, and gathering evidence before proposing fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I perform root-cause analysis for debugging production issues?▼

Root-cause analysis for debugging production issues is performed through a four-phase workflow: investigating root causes, analyzing patterns, testing hypotheses, and implementing fixes using error messages, logs, and data tracing.

What is the best way to troubleshoot errors in a multi-component software architecture?▼

Troubleshooting errors in a multi-component software architecture requires reading error messages, reproducing the issue reliably, inspecting recent changes, and collecting evidence before proposing any fixes to reduce toil and rework.

How do I verify a debugging fix and prevent regressions?▼

To verify a debugging fix and prevent regressions, create a failing test, implement the fix, verify the results, and validate regression risk during the implementation phase of the debugging workflow.

Can I use structured debugging to trace data across multiple system components?▼

Structured debugging supports tracing data across multiple system components by applying techniques like root-cause-tracing, defense-in-depth, and condition-based-waiting to reliably reproduce errors and validate fixes.

Why does random debugging mask the actual root cause of software errors?▼

Random debugging masks the actual root cause because it lacks structured evidence collection and pattern analysis, leading to premature fixes that waste time and introduce rework instead of isolating the true error source.