skills.rest
icyzh
icyzhCOMMUNITY
Explore all skills by this author →
Website𝕏@icyzhbeGitHub

systematic-debugging

Enforce a four-phase debugging methodology to identify and resolve root causes.

1|Updated Jul 31, 2026
Search Tags:#testing#debugging#investigation#troubleshooting#problem-solving#root-cause
One-click install
npx skills add https://github.com/icyzh/hermes-web --skill systematic-debugging-icyzh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/icyzh/hermes-web/tree/main/skills/software-development/systematic-debugging
Command: npx skills add https://github.com/icyzh/hermes-web --skill systematic-debugging-icyzh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the cycle of guessing and patching symptoms by enforcing a rigorous, four-phase investigation process that ensures bugs are understood before any code is changed.

Core Features & Use Cases

  • Root Cause Investigation: Provides a structured framework to read error messages, trace data flow, and build deterministic feedback loops.
  • Scientific Hypothesis Testing: Guides the user to form ranked, falsifiable hypotheses and test them one variable at a time.
  • Use Case: When a production bug is reported, use this skill to construct a tight reproduction script, isolate the failing component, and verify the fix with a regression test, preventing the common trap of introducing new bugs through hasty patches.

Quick Start

Use the systematic-debugging skill to investigate the failing test case in the current directory by following the four-phase process.

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 production bug instead of patching symptoms?▼

Root cause analysis for production bugs requires a systematic debugging methodology that enforces rigorous evidence gathering and isolated hypothesis testing to ensure durable fixes.

How do I debug a failing test case systematically without introducing new issues?▼

To debug a failing test case, follow a four-phase investigation process: systematically reproduce the failure, gather evidence, form falsifiable hypotheses, and verify the fix with a regression test.

How does scientific hypothesis testing work for troubleshooting software problems?▼

Scientific hypothesis testing for troubleshooting software problems involves forming ranked, falsifiable hypotheses and testing them one variable at a time to isolate the failing component.

Can I use systematic debugging for performance regressions and test failures, or only production bugs?▼

Systematic debugging applies to performance regressions and test failures alongside production bugs, enforcing a structured framework to trace data flow and build deterministic feedback loops.

Why do my quick bug fixes keep causing new problems in my software development workflow?▼

Quick bug fixes cause new problems because they patch symptoms without understanding the root cause; a rigorous investigation process with deterministic feedback loops prevents hasty patches.

How do I build a tight reproduction script to isolate a failing component?▼

Building a tight reproduction script requires systematic reproduction of the issue and evidence gathering to trace data flow, enabling you to isolate the failing component before applying fixes.

Related Skills

Explore More Software Engineering Skills→
unclehowellunclehowell

systematic-debugging

Diagnose software bugs through a four-phase root-cause investigation process.

Community
Advanced
MichaelSolatiMichaelSolati

diagnose

Guide structured 6-phase debugging for elusive bugs and performance regressions.

Community
Advanced
juliuss1907juliuss1907

systematic-debugging

Automate root cause analysis and systematic debugging across four investigation phases.

Community
Advanced
icartshicartsh
4

error-detective

Parse stack traces and guide error resolution with the TRACE framework.

Community
Advanced