skills.rest
CenredJun
CenredJunCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Trace root causes behind bugs using a four-phase workflow with evidence gathering and verification.

Updated Mar 27, 2026
Search Tags:#debugging#investigation#diagnostics#root-cause#software-engineering
One-click install
npx skills add https://github.com/CenredJun/openclaw-claudecode-setup-kit --skill systematic-debugging-cenredjun
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/CenredJun/openclaw-claudecode-setup-kit/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/CenredJun/openclaw-claudecode-setup-kit --skill systematic-debugging-cenredjun

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematic Debugging provides a disciplined framework to identify the root cause of software issues before attempting fixes, reducing wasted effort and rework.

Core Features & Use Cases

  • Phase-based investigation (Phase 1: Root Cause Investigation, Phase 2: Pattern Analysis, Phase 3: Hypothesis and Testing, Phase 4: Implementation) to structure debugging sessions.
  • Evidence-driven diagnosis: reproduce issues, inspect errors, log data across components, and trace data flow to origin.
  • Real-world use: for test failures, production bugs, and performance anomalies where quick guesses are risky and time is precious.

Quick Start

Describe a bug you observed, reproduce it consistently, gather diagnostic data, and begin Phase 1 root-cause investigation.

Frequently Asked Questions about systematic-debugging

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

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

Systematic debugging structures root cause investigation into four phases: evidence gathering, pattern analysis, hypothesis testing, and implementation. This enforces data-driven verification across multi-component environments before applying durable fixes.

What is the best way to debug integration issues across multi-component environments?▼

Debugging multi-component integration issues requires tracing data flow to its origin using instrumentation and logs. Pattern analysis identifies failure points across components before hypothesis testing verifies the exact anomaly source.

How do I fix failing tests without wasting effort on incorrect guesses?▼

Fix failing tests by reproducing them consistently and gathering diagnostic data to start root cause investigation. Pattern analysis and hypothesis testing prevent wasted effort by verifying the failure mechanism before implementation.

Does systematic debugging work for performance anomalies or only functional bugs?▼

Systematic debugging applies to performance anomalies and functional bugs alike. The evidence-driven workflow of root cause investigation, pattern analysis, hypothesis testing, and verified implementation handles any issue where quick guesses are risky.

When should I not use a phase-based debugging approach for software issues?▼

Avoid phase-based debugging when the root cause is immediately obvious from the error. The structured workflow targets complex test failures, production anomalies, and integration issues where quick guesses risk causing rework.

Related Skills

Explore More Software Engineering Skills→
tutur3ututur3u
53

systematic-debugging

Enforce root-cause investigation before fixing software bugs.

Official
Advanced
YangYuS8YangYuS8

systematic-debugging

Identify and isolate root causes of bugs before proposing fixes.

Community
Advanced
DhumitechDhumitech

systematic-debugging

Coordinate structured debugging workflows to identify root causes in production environments.

Community
Advanced
KaimingWanKaimingWan
103

omk-debugging

Enforce a root-cause investigation workflow with structured evidence and stage gates.

Community
Advanced