skills.rest
zhuyingcoder
zhuyingcoderCOMMUNITY
Explore all skills by this author →
GitHub

systematic_debugging

Enforce root-cause analysis before fixes in software debugging workflows.

Updated Apr 12, 2026
Search Tags:#testing#debugging#defense-in-depth#systematic#flows#root-cause
One-click install
npx skills add https://github.com/zhuyingcoder/cc-demo --skill systematic-debugging-zhuyingcoder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic_debugging
Source: https://github.com/zhuyingcoder/cc-demo/tree/main/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/zhuyingcoder/cc-demo --skill systematic-debugging-zhuyingcoder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging helps teams avoid patching symptoms by enforcing a four-phase process to identify the root cause of bugs, test failures, and abnormal behavior before proposing fixes.

Core Features & Use Cases

  • Four-phase workflow: root-cause investigation, pattern analysis, hypothesis validation, and implementation.
  • Anti-patterns and bulletproofing to resist time-pressure shortcuts.
  • Defense-in-depth style checks and testing guidance for reliability in complex systems.
  • Use cases include production incidents, flaky tests, cross-service failures, and difficult-to-trace bugs.

Quick Start

Load the Systematic Debugging skill and follow the Phase 1 checklist to begin root-cause investigation before proposing any fix.

Frequently Asked Questions about systematic_debugging

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

FAQPage Schema
How do I fix flaky tests by finding the root cause instead of patching symptoms?▼

Root-cause debugging enforces a four-phase process—investigation, pattern analysis, hypothesis validation, and implementation—to resolve flaky tests before applying any fixes.

What is the best way to debug production incidents across multi-service failures?▼

Systematic debugging handles multi-service failures by applying pattern analysis and defense-in-depth checks during root-cause investigation, preventing symptom patching during time-pressure incidents.

How do I start a systematic root-cause investigation for failing builds?▼

Begin root-cause investigation for failing builds by loading the debugging workflow and following the Phase 1 checklist to enforce hypothesis validation before any implementation.

Why should I use a systematic debugging workflow for difficult-to-trace bugs?▼

A systematic debugging workflow provides anti-patterns and bulletproofing to resist time-pressure shortcuts, ensuring you validate hypotheses and implement defense-in-depth checks for reliable fixes.

Can I apply root-cause analysis to cross-service failures during testing?▼

Yes, root-cause analysis applies to cross-service failures across development, testing, and production, using pattern analysis and testing-guided workflows to validate fixes.

What are the limitations of relying on systematic debugging for complex system failures?▼

Systematic debugging requires strictly following four phases without shortcuts, meaning time-pressure constraints may challenge teams needing immediate patches for complex system failures.

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
dmulcaheydmulcahey

systematic-debugging

Trace software bugs to root causes using a four-phase investigation methodology.

Community
Advanced
juliuss1907juliuss1907

systematic-debugging

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

Community
Advanced
DarkArty07DarkArty07
3

systematic-debugging

Investigate root cause of technical issues before implementing any code changes.

Community
Advanced