Does this skill require specific testing frameworks?

No, it is framework-agnostic. While it recommends using the test-driven development skill, it can be applied using any automated test suite or even one-off test scripts.

How does the skill handle bugs in multi-layer systems?

It implements diagnostic instrumentation at each component boundary to log data entry and exit, identifying exactly which layer the failure occurs in.

What happens if a fix fails more than three times?

The process mandates a stop to question the underlying architecture, preventing 'thrashing' and encouraging a discussion about potential design flaws rather than continuing to patch symptoms.

When should I use this skill instead of standard debugging?

Use it for any technical issue, especially under time pressure, when a 'quick fix' seems obvious but hasn't worked, or when dealing with complex multi-component systems.

What is the core principle of the Systematic Debugging skill?

The core principle is to always find the root cause before attempting any fix. Symptom-only fixes are discouraged as they often mask underlying issues.

Systematic Debugging

Name: Systematic Debugging
Author: zerdos

byzerdos

0•

보안 및 테스팅

Implements a rigorous four-phase workflow to identify root causes and eliminate bugs without introducing new regressions.

This skill transforms the debugging process from guesswork into a scientific method by enforcing a strict 'Root Cause First' rule. It guides Claude through evidence gathering, pattern analysis, and minimal hypothesis testing before any code changes are proposed. Highly effective for complex systems, production incidents, or persistent issues where previous fix attempts have failed, it ensures that every solution addresses the underlying problem rather than just masking symptoms, ultimately reducing technical debt and developer frustration.

주요 기능

01Automated 'Architectural Check' trigger that stops the cycle after three failed fix attempts

02Strict four-phase debugging framework: Investigation, Pattern, Hypothesis, and Implementation

030 GitHub stars

04Mandatory failing test case creation to verify fixes and prevent future regressions

05Diagnostic instrumentation for multi-component systems to pinpoint boundary failures

06Backward data flow tracing to locate the original trigger of corrupted application state

사용 사례

01Troubleshooting deep call stack errors where the source of invalid data is unknown

02Resolving intermittent production bugs that are difficult to reproduce consistently

03Debugging complex CI/CD pipeline failures or environment-specific configuration issues

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add zerdos/superpowers systematic-debugging

For use in Claude.ai and ChatGPT

주요 기능

01Automated 'Architectural Check' trigger that stops the cycle after three failed fix attempts

02Strict four-phase debugging framework: Investigation, Pattern, Hypothesis, and Implementation

030 GitHub stars

04Mandatory failing test case creation to verify fixes and prevent future regressions

05Diagnostic instrumentation for multi-component systems to pinpoint boundary failures

06Backward data flow tracing to locate the original trigger of corrupted application state

사용 사례

01Troubleshooting deep call stack errors where the source of invalid data is unknown

02Resolving intermittent production bugs that are difficult to reproduce consistently

03Debugging complex CI/CD pipeline failures or environment-specific configuration issues