skills.rest
huangwb8
huangwb8COMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Diagnoses bugs via a four-phase root-cause framework with evidence-based analysis and testing.

47|8|Updated Jan 3, 2026
Search Tags:#debugging#root-cause#evidence-based#five-whys#production-debugging#stack-trace#hypothesis-testing
One-click install
npx skills add https://github.com/huangwb8/skills --skill systematic-debugging-huangwb8
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/huangwb8/skills/tree/main/awesome-code/agents/systematic-debugging
Command: npx skills add https://github.com/huangwb8/skills --skill systematic-debugging-huangwb8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides engineers to debug bugs methodically using a four-phase root-cause framework, ensuring that fixes target the underlying cause rather than symptoms.

Core Features & Use Cases

  • Four-phase debugging workflow (root-cause investigation, pattern analysis, hypothesis testing, implementation) to replace patch-and-pray fixes.
  • Comprehensive evidence collection and structured reasoning for reliable root-cause tracing.
  • Applicable to bugs, test failures, flaky tests, or production issues; helps teams reduce regression risk and improve debugging discipline.
  • Use Case: When facing a failing test or production bug, follow the framework to locate root cause and implement a minimal fix with regression checks.

Quick Start

Describe the failing behavior you want to fix, then apply the four-phase framework to identify the root cause before attempting any changes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
How do I find the root cause of a production bug instead of just patching symptoms?▼

Root-cause debugging applies a four-phase framework—data collection, hypothesis formation, controlled testing, and verified fixes—to trace underlying causes using evidence-based analysis and five-why style investigation.

What is the best way to debug flaky tests and inconsistent test failures methodically?▼

Debug flaky tests by collecting comprehensive evidence, forming hypotheses, and running controlled tests to validate assumptions before implementing minimal fixes with regression checks.

How do I stop recurring regressions when fixing errors in development and testing environments?▼

Prevent recurring regressions by enforcing evidence-based investigations with lightweight validation, regression testing, and defensive design during the bug fixing workflow.

Does root-cause debugging work for diagnosing stack traces and production issues without patch-and-pray fixes?▼

Yes, root-cause debugging replaces patch-and-pray fixes by applying structured reasoning and pattern analysis to diagnose stack traces and production issues reliably.

When do I need a systematic debugging framework for tracing errors?▼

Use a systematic debugging framework when facing failing tests, production bugs, or inconsistent behavior that requires evidence-based analysis and structured root-cause tracing rather than quick patches.

Related Skills

Explore More Software Engineering Skills→
Ilenburg1993Ilenburg1993
3

reactive-bug-audit

Analyze stack traces and logs to identify root causes and apply minimal patches.

Community
Intermediate
StudentCristianStudentCristian

nw-bugfix

Coordinate root-cause analysis, user validation, and regression testing for defect resolution.

Community
Advanced
bordenetbordenet
8

reproduction-experiment-investigator

Reproduce controlled experiments to validate debugging hypotheses and generate structured evidence.

Community
Advanced
romiluz13romiluz13
161

root-cause-analysis

Guide root cause analysis through evidence collection and hypothesis testing.

Community
Basic