systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: tc9011

Guide structured four-phase debugging to identify and resolve root causes.

Updated Feb 5, 2026

Search Tags:#debugging #root cause #problem solving #troubleshooting #software development #bug fixing

Ready to run

npx skills add https://github.com/tc9011/my-skills --skill systematic-debugging-tc9011

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/tc9011/my-skills/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/tc9011/my-skills --skill systematic-debugging-tc9011

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents time-wasting "quick fixes" that mask symptoms and introduce new bugs. It guides users to systematically identify and resolve the root cause of any technical issue, ensuring robust and lasting solutions.

Core Features & Use Cases

Four-Phase Process: Guides through Investigation, Pattern Analysis, Hypothesis, and Implementation.
Root Cause Mandate: Emphasizes finding the fundamental issue, not just treating symptoms.
Pressure Resistance: Includes anti-patterns and specific language to resist rationalization under time pressure.
Use Case: When a critical API is failing in production, use this Skill to ensure the actual root cause is found and fixed, rather than applying a temporary patch that might fail again later.

Quick Start

Use the systematic debugging skill to investigate any bug or unexpected behavior before proposing fixes.

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

Systematic debugging prevents time-wasting quick fixes by guiding you through a structured four-phase process: investigation, pattern analysis, hypothesis testing, and implementation. This ensures you resolve the fundamental issue rather than applying temporary patches.

How do I debug a failing production API under time pressure without introducing new issues?▼

To debug a failing production API under pressure, follow a systematic debugging process that includes specific anti-patterns to resist rationalization. This enforces root cause identification before implementation, preventing rushed patches that introduce new bugs.

How do I troubleshoot unexpected behavior in a multi-component system?▼

Troubleshooting multi-component systems requires a structured debugging approach with specific guidance for investigating complex interactions. You systematically identify patterns and test hypotheses across components to isolate the root cause of the unexpected behavior.

Why does my bug fix keep failing or causing new bugs in production?▼

Bug fixes fail or cause new issues when they treat symptoms instead of the root cause. A systematic debugging process prevents this by enforcing pattern analysis and hypothesis testing before implementation, ensuring the fundamental technical issue is fully resolved.

When should I use a systematic debugging process instead of applying a quick fix?▼

Use systematic debugging whenever you face unexpected technical behavior or a critical failure. It prevents the common pitfall of applying quick fixes that mask symptoms and ensures robust, lasting solutions by finding the root cause.