systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: Fancu

Guide users through a four-phase debugging process to identify root causes.

Updated Dec 11, 2025

Search Tags:#debugging #root cause #troubleshooting #error handling #bug fixing #systematic process

Ready to run

npx skills add https://github.com/Fancu1/dotfile --skill systematic-debugging-fancu1

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents wasted time and new bugs caused by quick fixes or symptom-based solutions, ensuring that the true root cause of any issue is identified and addressed before any fixes are implemented.

Core Features & Use Cases

Structured Debugging Process: Guides users through four mandatory phases: Investigation, Pattern Analysis, Hypothesis, and Implementation.
Root Cause Mandate: Emphasizes finding the underlying issue rather than just patching symptoms.
Pressure Resistance: Includes specific language and structural defenses to prevent shortcuts under time pressure or perceived urgency.
Use Case: When a critical API endpoint starts returning errors, instead of immediately trying a quick fix, use this Skill to systematically investigate, identify the exact point of failure in the data flow, form a hypothesis, and then implement a targeted fix.

Quick Start

Use the systematic debugging skill when encountering any bug or unexpected behavior before proposing any fixes.

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 the symptom?▼

Systematic debugging requires tracing data flow and gathering evidence before proposing fixes. You must investigate the exact point of failure, analyze patterns, and form hypotheses to identify the underlying issue rather than patching symptoms.

What is the best way to debug an API endpoint returning unexpected errors?▼

Debugging an API endpoint requires investigating the exact point of failure in the data flow, analyzing error patterns, forming a hypothesis about the root cause, and implementing a targeted fix rather than attempting quick patches under time pressure.

How do I stop myself from taking debugging shortcuts when under time pressure?▼

To resist time pressure during debugging, follow a structured four-phase process with explicit rules against rationalization and shortcuts. This ensures thorough evidence gathering and hypothesis formation before implementation, preventing symptom-based quick fixes.

What should I do when my bug fixes keep failing and introducing new issues?▼

When multiple bug fixes fail, escalate to architectural questioning and rigorous data flow tracing. A systematic debugging process enforces root cause identification through pattern analysis and hypothesis formation before implementation, preventing new issues from symptom patching.

When should I use a systematic debugging process for troubleshooting?▼

Use systematic debugging for troubleshooting whenever encountering any bug or unexpected behavior, before proposing any fixes. It prevents wasted time and new bugs caused by symptom-based solutions by mandating root cause identification through structured investigation.