skills.rest
reiserwang
reiserwangCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Identify root causes of technical issues using a four-phase investigation model.

Updated Aug 27, 2026
Search Tags:#testing#debugging#investigation#troubleshooting#phases#root-cause
One-click install
npx skills add https://github.com/reiserwang/Coding_Agent --skill systematic-debugging-reiserwang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/reiserwang/Coding_Agent/tree/main/.gemini/skills/systematic-debugging
Command: npx skills add https://github.com/reiserwang/Coding_Agent --skill systematic-debugging-reiserwang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging provides a disciplined, phase-driven approach to identify root causes before attempting fixes, reducing wasted effort and rework.

Core Features & Use Cases

  • Enforces a four-phase debugging process: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation
  • Produces explicit root-cause statements and traceable outcomes to guide fixes
  • Applies to bugs, flaky tests, performance issues, and integration problems across software projects

Quick Start

Start by reproducing the issue and gathering evidence to identify the root cause before proposing fixes.

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 bug before attempting a fix?▼

To find the root cause of a bug, reproduce the issue and gather logs and traces. A four-phase investigation model isolates components and tests hypotheses to ensure traceable fixes and reduce wasted effort.

What is a systematic debugging process for troubleshooting software issues?▼

A systematic debugging process applies a four-phase model: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation to diagnose technical issues across diverse environments.

How do I troubleshoot flaky tests and performance issues across diverse environments?▼

Troubleshoot flaky tests and performance issues by reproducing them and collecting traces. Isolate components through pattern analysis and hypothesis testing to produce explicit root-cause statements.

What's the best way to investigate integration problems without wasting effort on incorrect patches?▼

Investigate integration problems by enforcing a phase-driven approach that identifies root causes before implementation. This prevents wasted effort and rework by producing explicit root-cause documentation and traceable outcomes.

Does this root-cause investigation method work for any software project?▼

Yes, this root-cause investigation method works across diverse software projects, applying to bugs, flaky tests, performance issues, and integration problems without requiring specific dependencies or components.

Related Skills

Explore More Software Engineering Skills→
a-ariffa-ariff
14

root-cause-tracing

Trace bugs backward from symptoms to identify root causes.

Community
Intermediate
JackSmack1971JackSmack1971

debug-root-cause-analysis

Guide structured root-cause debugging through observe, reproduce, hypothesize, test, fix, verify, and prevent phases.

Community
Advanced
timurgaleevtimurgaleev
5

investigate

Guide structured root-cause debugging through phases for context, analysis, hypothesis, and verification.

Community
Advanced
Chang-Shih-YungChang-Shih-Yung

gstack-openclaw-investigate

Enforces a four-phase root cause workflow for web and backend system debugging.

Community
Advanced