systematic-debugging

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

3|Updated Feb 21, 2026

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

Ready to run

npx skills add https://github.com/lucasgrow/some-skills --skill systematic-debugging-lucasgrow

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents wasted time and new bugs caused by random fixes and quick patches, ensuring that the true root cause of any issue is identified and addressed before any implementation.

Core Features & Use Cases

Systematic Four-Phase Process: Guides users through Investigation, Pattern Analysis, Hypothesis, and Implementation.
Root Cause Mandate: Emphasizes finding the underlying issue, not just fixing surface-level symptoms.
Pressure Resistance: Includes explicit rules and language to prevent shortcuts under time pressure or urgency.
Use Case: When a critical bug appears in production, this Skill ensures a thorough investigation to prevent recurring issues, rather than applying a temporary workaround that might mask the real problem.

Quick Start

Use the systematic-debugging skill to investigate any bug before proposing 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 software bug instead of just fixing symptoms?▼

A systematic debugging process prevents recurring issues by guiding you through investigation, pattern analysis, hypothesis formation, and implementation to identify the true root cause before any fixes are applied.

What is the best way to debug critical production issues under time pressure?▼

Debugging critical production issues under time pressure requires a systematic process with explicit rules to resist shortcuts, preventing quick patches that mask the real problem and ensuring the root cause is addressed.

How do I trace data flow across multiple components when troubleshooting an error?▼

Troubleshooting errors across multiple components requires a systematic debugging process that supports complex systems, guiding you through multi-component data flow tracing with environment guardrails to isolate the root cause.

Why do my quick patches keep causing new bugs and recurring issues?▼

Quick patches cause new bugs and recurring issues because they address surface-level symptoms rather than the root cause. A systematic debugging process ensures the underlying issue is identified and resolved before implementation.

What are the steps in a systematic debugging process for complex technical issues?▼

The steps in a systematic debugging process for complex technical issues are investigation, pattern analysis, hypothesis formation, and implementation. This four-phase process ensures thorough root cause identification and resolution.

When should I avoid symptom-fixing and perform a full root cause analysis?▼

You should avoid symptom-fixing and perform a full root cause analysis whenever a critical bug appears in production. A systematic debugging process prevents wasted time and new bugs caused by random fixes and quick patches.