systematic-debugging

Diagnose software failures through root-cause analysis across multi-component systems.

4|Updated Dec 5, 2025

Search Tags:#debugging #troubleshooting #reproducibility #root-cause #software-engineering #error-analysis

Ready to run

npx skills add https://github.com/aaaa47080/stock_agent --skill systematic-debugging-aaaa47080

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/aaaa47080/stock_agent/tree/main/.opencode/skills/systematic-debugging
Command: npx skills add https://github.com/aaaa47080/stock_agent --skill systematic-debugging-aaaa47080

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging provides a disciplined, four-phase framework to diagnose bugs and failures, ensuring root causes are identified before applying changes.

Core Features & Use Cases

Phase-driven approach: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation.
Evidence gathering and reproducibility: collect logs, traces, and test results to validate findings.
Guardrails against quick fixes: prevents premature changes by requiring data-backed conclusions.
Applicable to multi-component systems and CI pipelines: works across local dev, services, and orchestration layers.

Quick Start

Initiate the four-phase process by collecting error messages, reproducing the failure, and documenting findings to begin root-cause analysis.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is the best way to find the root cause of a software bug instead of guessing?▼

Systematic debugging identifies root causes by guiding you through evidence collection, reproducibility checks, and hypothesis testing across multi-component systems before applying any fixes.

How do I debug test failures and build errors in a CI pipeline?▼

Debug CI pipeline failures by collecting logs, traces, and test results, then validating reproducibility to isolate the failing component before implementing minimal-risk fixes.

How do I troubleshoot unexpected behavior across distributed services?▼

Troubleshoot distributed services through a four-phase root cause investigation: gather evidence, analyze failure patterns, test hypotheses, and implement data-backed fixes.

Can I use this systematic debugging approach for local development environments?▼

Yes, this debugging approach works across local development, CI pipelines, and orchestration layers, requiring only error messages and reproducible failure states to begin analysis.

Why should I avoid quick fixes when resolving software failures?▼

Quick fixes risk introducing regressions because they bypass root cause analysis; this framework enforces guardrails requiring data-backed conclusions and validated reproducibility before changes.

How do I start a root cause investigation for an error analysis?▼

Begin root cause investigation by collecting error messages, reproducing the failure condition, and documenting findings to establish an evidence baseline for pattern analysis.