systematic-debugging

Guide a four-phase debugging process to identify root causes of software issues.

Updated Aug 23, 2026

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

Ready to run

npx skills add https://github.com/juliuschun/tower --skill systematic-debugging-juliuschun

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a structured, step-by-step process to systematically identify the root cause of bugs, test failures, or unexpected behavior, preventing the common pitfall of only fixing symptoms.

Core Features & Use Cases

Four-Phase Framework: Guides users through Investigation, Pattern Analysis, Hypothesis, and Implementation.
Pressure Resistance: Includes specific rules and language designed to prevent shortcuts under time pressure.
Anti-Pattern Identification: Clearly outlines common mistakes and rationalizations to avoid.
Use Case: When a critical test fails in CI and the error message is cryptic, load this skill to ensure a thorough investigation rather than a quick, potentially incorrect fix.

Quick Start

Use the systematic debugging skill to find the root cause of the current bug.

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 symptoms?▼

Systematic debugging identifies the root cause of software issues by guiding you through a four-phase process: Investigation, Pattern Analysis, Hypothesis, and Implementation. This structured approach prevents the common pitfall of only fixing symptoms instead of addressing the underlying cause.

What is the best way to troubleshoot cryptic test failures in CI?▼

The best way to troubleshoot cryptic test failures is to apply a structured debugging framework that resists time pressure. By systematically investigating patterns and testing hypotheses, you ensure a thorough analysis rather than deploying a potentially incorrect, rushed fix.

How do I systematically debug unexpected software behavior?▼

You systematically debug unexpected software behavior by following a four-phase framework: Investigation, Pattern Analysis, Hypothesis, and Implementation. This process enforces thorough investigation and controlled implementation to accurately resolve the issue.

Why does my bug fix keep causing new issues under time pressure?▼

Bug fixes cause new issues under time pressure when developers take shortcuts and only fix symptoms. A systematic debugging approach includes specific rules to resist this pressure, ensuring you verify the root cause through pattern analysis and hypothesis testing before implementing changes.

What are common anti-patterns to avoid during software troubleshooting?▼

Common anti-patterns during software troubleshooting include taking shortcuts under time pressure and rationalizing superficial fixes. A systematic debugging process clearly outlines these mistakes to avoid, ensuring you implement controlled changes based on verified hypotheses.

When do I need a systematic debugging process for bug fixing?▼

You need a systematic debugging process for bug fixing when facing critical test failures, cryptic error messages, or unexpected behavior. It is essential when you want to prevent recurring symptoms and ensure controlled, accurate implementation of your fix.