skills.rest
Hieubkav
HieubkavCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Systematic Debugging

Identify root causes of bugs across multi-component software systems.

Updated Oct 26, 2025
Search Tags:#debugging#root cause#phase-based
One-click install
npx skills add https://github.com/Hieubkav/wincellarCloneBackend --skill systematic-debugging-hieubkav
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Systematic Debugging
Source: https://github.com/Hieubkav/wincellarCloneBackend/tree/main/.claude/skills/workflows/systematic-debugging
Command: npx skills add https://github.com/Hieubkav/wincellarCloneBackend --skill systematic-debugging-hieubkav

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

A four-phase debugging framework to ensure root-cause investigation before fixes.

Core Features & Use Cases

  • Phase 1: Root Cause Investigation
  • Phase 2: Pattern Analysis
  • Phase 3: Hypothesis & Testing
  • Phase 4: Implementation
  • Anti-patterns and stop rules to prevent rushed fixes

Quick Start

Load skill and apply Phase 1 checklist to start root-cause diagnosis.

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 instead of just fixing symptoms?▼

Root-cause debugging isolates what actually triggered a bug before attempting fixes. This framework uses a four-phase workflow—Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation—requiring Phase 1 completion first to avoid rushed, symptom-driven solutions that leave underlying issues unresolved.

What's the best way to debug test failures and build failures across multiple components?▼

Systematic debugging applies a structured approach to any technical issue—bugs, test failures, performance problems, build failures, and unexpected behavior—across multi-component systems. It mandates diagnostic data collection and evidence-based analysis before moving to solutions, preventing incomplete fixes.

How do I avoid common debugging mistakes and shortcuts?▼

The framework includes explicit anti-patterns and stop rules designed to resist common debugging shortcuts. These guardrails keep investigation focused on root causes rather than surface-level symptoms, ensuring your fixes address actual problems rather than temporary workarounds.

Can I use this debugging approach for performance problems and unexpected behavior?▼

Yes, this four-phase framework applies to all technical issues—bugs, test failures, performance degradation, build failures, and unexpected behavior. The methodology is domain-agnostic and works across different software architectures and component interactions.

What should I do after identifying the root cause?▼

After Phase 1 Root Cause Investigation, proceed through Pattern Analysis to identify related occurrences, then develop and test hypotheses in Phase 3 before implementing fixes in Phase 4. This sequence ensures targeted, evidence-backed solutions rather than isolated patches.

Related Skills

Explore More Software Engineering Skills→
joshua3403joshua3403

systematic-debugging

Guide engineers through a four-phase root-cause debugging workflow.

Community
Advanced
baleen37baleen37
10

defense-in-depth

Add validation at four layers to prevent bug recurrence.

Community
Intermediate
allexcdallexcd

autonomous-bug-fixing

Diagnose, reproduce, and fix code defects from bug reports or error logs.

Community
Advanced
LISANG3LISANG3
1

systematic-debugging

Guides users through a four-phase systematic debugging process to identify root causes of technical issues.

Community
Advanced