skills.rest
eddielueng
eddieluengCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide root-cause investigation for technical bugs and test failures.

1|Updated Apr 14, 2026
Search Tags:#debugging#test failures#incident response#regression testing#root-cause analysis#software troubleshooting#data flow tracing
One-click install
npx skills add https://github.com/eddielueng/hermes-agent-zh --skill systematic-debugging-eddielueng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/eddielueng/hermes-agent-zh/tree/main/skills/software-development/systematic-debugging
Command: npx skills add https://github.com/eddielueng/hermes-agent-zh --skill systematic-debugging-eddielueng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Systematic debugging prevents wasted time and new regressions by forcing root-cause investigation before any code changes.

Core Features & Use Cases

  • Four-phase root-cause workflow: Read errors, reproduce reliably, inspect recent changes, and trace data flow to isolate the failing component before proposing solutions.
  • Pattern analysis against working examples: Compare broken behavior to similar working code paths and identify real differences.
  • Hypothesis-driven minimal testing: Form a single hypothesis, test it with the smallest possible change, and only proceed when the hypothesis is verified.
  • Test-first repair and verification: Create a failing regression test, implement a single fix at the root cause, and validate to ensure no regressions.
  • Multi-component evidence gathering: Add diagnostic instrumentation across boundaries (API/service/database, CI/build/deploy) to determine where the system breaks.

Quick Start

Use systematic-debugging when you see a test failure and ask: "Investigate the root cause of this error using the four phases, and do not propose any fixes until the failing component and cause are isolated."

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 test failures instead of guessing fixes?▼

Root-cause analysis for test failures requires a systematic debugging workflow: gathering evidence, analyzing patterns against working code, testing hypotheses with minimal changes, and implementing test-first fixes to prevent regressions.

How do I debug failures across multi-component systems like CI pipelines or API-to-database flows?▼

Debugging multi-component systems involves adding diagnostic instrumentation across boundaries to trace data flow, isolating the failing component by comparing broken behavior to working code paths before proposing any code changes.

How do I stop regressions when troubleshooting software bugs in deep call stacks?▼

Software troubleshooting for deep call stacks requires forming a single hypothesis, testing it with the smallest possible change, creating a failing regression test, and validating that a single root-cause fix resolves the issue without new regressions.

When should I use a systematic debugging workflow instead of directly patching errors?▼

A systematic debugging workflow is needed when you see test failures and want to avoid guess-and-check fixes, ensuring you read errors, reproduce reliably, inspect recent changes, and isolate the failing component before proposing solutions.

Does root-cause analysis work for incident response and regression testing in complex codebases?▼

Root-cause analysis applies to incident response and regression testing across complex codebases by forcing evidence gathering, pattern analysis, hypothesis testing, and test-first verification steps before any fix is implemented.

Related Skills

Explore More Software Engineering Skills→
derHakenderHaken
437

systematic-debugging

Trace data flow and apply a four-phase process to fix root causes.

Community
Advanced
eugenelimeugenelim
15

bug-fix

...

Community
Advanced
quiznatquiznat

systematic-debugging

Identify and isolate root causes of software bugs through phased hypothesis testing.

Community
Advanced
RDCrystalLabRDCrystalLab

debug-hypothesis

Structure debugging investigations with evidence-driven root cause analysis.

Official
Advanced