systematic-debugging

Guide root cause analysis through investigation, pattern identification, hypothesis testing, and implementation.

Updated Mar 6, 2026

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

Ready to run

npx skills add https://github.com/ryan-ressmeyer/llm-skills --skill systematic-debugging-ryan-ressmeyer

💬 Prompt for ChatGPT / Claude Chat▼

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

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 by ensuring you always find the root cause of an issue before attempting any fixes, especially under pressure.

Core Features & Use Cases

Structured Debugging: Guides you through a mandatory four-phase process: Investigation, Pattern Analysis, Hypothesis, and Implementation.
Pressure Resistance: Includes specific rules and language to combat rationalization during emergencies or tight deadlines.
Use Case: When a critical API endpoint starts returning errors, use this skill to systematically trace the problem from the error message back to the original faulty code, rather than just adding a quick, temporary workaround.

Quick Start

When encountering any bug, load the systematic-debugging skill and follow its four-phase process 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 software bug instead of just fixing symptoms?▼

Use a structured debugging methodology that enforces a four-phase process: Investigation, Pattern Analysis, Hypothesis, and Implementation. This systematic approach forces you to trace the root cause before applying fixes, preventing wasted time on symptoms.

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

The best way to debug critical errors under time pressure is to use a systematic process with specific pressure-resistance rules. These rules combat rationalization during emergencies, ensuring you still identify the root cause rather than applying quick temporary workarounds.

How do I troubleshoot a complex system when my bug fixes keep failing?▼

When bug fixes keep failing in a complex system, you should question the underlying architecture rather than applying more fixes. A systematic debugging process helps identify pattern failures and prompts architectural evaluation after multiple failed hypotheses.

How do I systematically trace an API endpoint error back to faulty code?▼

Systematically trace an API endpoint error by starting with the Investigation phase to gather context, followed by Pattern Analysis to identify anomalies, forming a Hypothesis about the faulty code, and finally implementing the fix in the last phase.

Why should I use a systematic debugging process instead of applying quick workarounds?▼

You should use a systematic debugging process because applying quick workarounds often fixes only symptoms, which can introduce new bugs and waste time. Finding the root cause first prevents regression and ensures the technical issue is fully resolved.