systematic-debugging

Guide software debugging through root cause investigation, pattern analysis, hypothesis formation, and implementation.

Updated Mar 26, 2025

Search Tags:#testing #debugging #investigation #root cause #troubleshooting #bug fixing

Ready to run

npx skills add https://github.com/GSU-FrankJ/tournament_experiment --skill systematic-debugging-gsu-frankj

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/GSU-FrankJ/tournament_experiment/tree/main/.cursor/skills/systematic-debugging
Command: npx skills add https://github.com/GSU-FrankJ/tournament_experiment --skill systematic-debugging-gsu-frankj

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents time wasted on superficial fixes by enforcing a rigorous, step-by-step process to identify and resolve the true root cause of any bug, test failure, or unexpected behavior.

Core Features & Use Cases

Mandatory Root Cause Analysis: Ensures investigation precedes any fix.
Four-Phase Process: Guides users through Investigation, Pattern Analysis, Hypothesis, and Implementation.
Pressure Resistance: Includes explicit rules and language to combat rationalization under time pressure.
Use Case: When a critical test fails in CI, instead of guessing, load this skill to systematically trace the failure back to its origin, ensuring a permanent fix and preventing future occurrences.

Quick Start

Use the systematic debugging skill to investigate the current test failure.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I systematically debug a failing test instead of guessing fixes?▼

To systematically debug a failing test, you need a structured methodology that enforces root cause investigation before any fixes. This process guides you through four phases: Investigation, Pattern Analysis, Hypothesis, and Implementation, preventing superficial symptom patching.

What is the best way to find the root cause of a software bug under time pressure?▼

Finding the root cause of a software bug under time pressure requires a pressure-resistant process with explicit rules against rationalization. By enforcing strict adherence to hypothesis formation and pattern analysis, you ensure a permanent solution rather than a rushed symptom fix.

Why does troubleshooting keep recurring after I patch the unexpected behavior?▼

Troubleshooting keeps recurring because fixing symptoms without identifying the true root cause leaves the underlying issue intact. A systematic debugging methodology forces you to trace the failure back to its origin, ensuring a permanent fix and preventing future occurrences.

What are the steps in a root cause investigation for software issues?▼

A root cause investigation for software issues follows four structured steps: Investigation to gather data, Pattern Analysis to identify trends, Hypothesis to form testable theories, and Implementation to apply the permanent fix. This prevents symptom-fixing.

When do I need a structured debugging process for CI test failures?▼

You need a structured debugging process for CI test failures when you want to prevent time wasted on superficial fixes. Loading a systematic investigation skill helps you trace the failure back to its origin, ensuring a permanent resolution instead of guessing.

Can I use this systematic debugging method for any unexpected software behavior?▼

Yes, you can use this systematic debugging method for any unexpected software behavior, bug, or test failure. It provides a rigorous, step-by-step process to identify and resolve the true root cause regardless of the specific error context.