skills.rest
KaimingWan
KaimingWanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Enforce a four-phase debugging process prioritizing root cause identification before fixes.

103|15|Updated Feb 6, 2026
Search Tags:#testing#debugging#troubleshooting#software development#root cause analysis#bug fixing
One-click install
npx skills add https://github.com/KaimingWan/oh-my-claude-code --skill systematic-debugging-kaimingwan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/KaimingWan/oh-my-claude-code/tree/main/archive/v2/claude-skills/systematic-debugging
Command: npx skills add https://github.com/KaimingWan/oh-my-claude-code --skill systematic-debugging-kaimingwan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the common issue of developers attempting quick fixes for bugs without first identifying the root cause, leading to recurring issues and wasted time.

Core Features & Use Cases

  • Root Cause Analysis: Enforces a structured, multi-phase approach to debugging.
  • Systematic Investigation: Guides users through error analysis, reproduction, change tracking, and data flow tracing.
  • Use Case: When a critical test fails in a CI pipeline, use this Skill to systematically investigate why, ensuring the underlying problem is solved rather than just the test passing temporarily.

Quick Start

Use the systematic-debugging skill to investigate the current bug.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is the best way to find the root cause of a software bug before fixing it?▼

Root cause analysis for a software bug requires a structured process that prioritizes identifying the underlying issue before proposing fixes. This approach enforces error analysis, reproduction, and evidence gathering to prevent recurring issues.

How do I debug a failing CI pipeline test systematically?▼

To debug a failing CI pipeline test systematically, follow a multi-phase process: analyze the error message, consistently reproduce the issue, correlate recent changes, and trace data flow across components to pinpoint the exact failure point.

Why do my bug fixes keep failing in multi-component systems?▼

Bug fixes in multi-component systems often fail when the root cause is missed. A systematic debugging process mandates tracing data flow and gathering evidence across components to ensure the underlying problem is actually solved.

When should I question my software architecture during troubleshooting?▼

You should question your software architecture during troubleshooting when multiple bug fixes fail. If repeated attempts to resolve an issue are unsuccessful, the systematic debugging process dictates a critical step to evaluate the architectural design.

How do I form and test a debugging hypothesis for error analysis?▼

Forming and testing a debugging hypothesis involves creating a minimal test based on gathered evidence. This structured troubleshooting step ensures you validate the root cause analysis through controlled testing before applying any actual code changes.

Related Skills

Explore More Software Engineering Skills→
gwozaigwozai

troubleshoot

Guide users through root cause analysis for software errors and bugs.

Community
Advanced
shaythegay13shaythegay13

investigate

Identify software issue root causes through symptom collection and code review.

Community
Advanced
murphytruemanmurphytrueman
155

cicd-integration

Generate CI/CD pipeline configurations for design system quality checks.

Community
Advanced
third774third774
5

systematic-debugging

Trace software issues to root causes using a four-phase debugging process.

Community
Advanced