systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: azmiariffaris

Guide a four-phase investigation to diagnose root causes of software bugs.

Updated Aug 27, 2026

Search Tags:#debugging #troubleshooting #root-cause #reproduction #data-flow #phase-based

Ready to run

npx skills add https://github.com/azmiariffaris/HERMES-AGENT --skill systematic-debugging-azmiariffaris

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/azmiariffaris/HERMES-AGENT/tree/main/snapshot/hermes/skills/software-development/systematic-debugging
Command: npx skills add https://github.com/azmiariffaris/HERMES-AGENT --skill systematic-debugging-azmiariffaris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a disciplined, phase-driven approach to debugging that emphasizes root-cause investigation before applying fixes, reducing wasted effort and rework.

Core Features & Use Cases

Four-phase framework: Phase 1 (Root Cause Investigation), Phase 2 (Pattern Analysis), Phase 3 (Hypothesis and Testing), Phase 4 (Implementation)
Guidance on reproducing errors, gathering evidence, tracing data flow, and validating findings
Optional delegation: structured prompts for multi-component debugging and testing workflows

Quick Start

Follow Phase 1 to start by reproducing the issue, collecting evidence, and tracing data flow to identify the root cause before fixes.

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 finding the root cause of software bugs?▼

Systematic debugging uses a four-phase method to find root causes: reproducing the issue, collecting evidence, tracing data flow, and validating a hypothesis before applying fixes. This reduces wasted effort and rework.

How do I debug a test failure or unexpected behavior in my codebase?▼

Start by reproducing the error and reviewing logs to gather evidence. Trace data flow across components to form a testable root-cause hypothesis before implementing any fixes, ensuring the actual issue is addressed.

Can I use this debugging method for CI pipelines and production environments?▼

Yes, this debugging method applies to any bug, test failure, or unexpected behavior across codebases, CI pipelines, and production environments. It guides reproducibility checks and evidence collection regardless of where the error occurs.

What's the best way to troubleshoot errors without randomly changing code?▼

Follow a phase-based investigation that enforces reviewing error messages, reproducing the issue, and tracing data flow. This structured evidence gathering prevents random fixes by requiring a validated root-cause hypothesis first.

How does a phase-based debugging framework handle multi-component issues?▼

The framework includes optional delegation with structured prompts for multi-component debugging. It guides tracing data flow and evidence collection across components to isolate the root cause during the investigation phases.

Why should I trace data flow before fixing a bug?▼

Tracing data flow before fixing a bug ensures you collect structured evidence and validate a root-cause hypothesis. This prevents patching symptoms and reduces the rework caused by applying untested fixes to complex codebases.