What is the 'Three Fix Rule' included in this skill?

If three or more attempts to fix a bug fail, the skill recognizes it as a potential architectural flaw rather than a simple bug. It then prompts an architectural review instead of continuing the cycle of failed patches.

Why does this skill prevent me from proposing an immediate fix?

This skill enforces the 'Iron Law' of debugging: root cause investigation must precede any code changes. This prevents 'fixing symptoms,' which usually masks deeper issues and leads to regressions.

Can this skill be used for performance issues?

Yes, the systematic phases apply to performance bottlenecks by requiring evidence-based investigation and hypothesis testing before modifying configuration or code.

How does the skill handle bugs that aren't consistently reproducible?

It guides you to gather evidence and add diagnostic instrumentation rather than guessing. By logging data at component boundaries, it helps transform intermittent failures into observable data points.

Systematic Debugging

Name: Systematic Debugging
Author: clsandoval

byclsandoval

0•

보안 및 테스팅

Implements a rigorous, four-phase methodology to identify root causes and eliminate software bugs without trial-and-error thrashing.

The Systematic Debugging skill for Claude Code enforces a disciplined approach to software troubleshooting by prohibiting code fixes until a root cause is definitively identified. It guides users through a structured process—Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation—to ensure that solutions address the source of a problem rather than its symptoms. By utilizing diagnostic instrumentation and backward data-flow tracing, this skill significantly reduces the introduction of secondary bugs and helps resolve complex issues in multi-component systems where simple patches often fail.

주요 기능

01Strict 'No Root Cause, No Fix' enforcement to prevent technical debt.

02Multi-component diagnostic instrumentation for tracing data across service boundaries.

03Scientific hypothesis testing using minimal variables to isolate failure points.

040 GitHub stars

05Architectural review triggers that stop infinite 'guess-and-check' loops after three failed attempts.

06Automated test-driven verification requirements for every implemented fix.

사용 사례

01Resolving intermittent test failures and race conditions in CI/CD pipelines.

02Debugging deep data-flow issues in microservices or multi-layered architectures.

03Identifying the source of performance regressions and build environment failures.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add clsandoval/monorepo systematic-debugging

For use in Claude.ai and ChatGPT

주요 기능

01Strict 'No Root Cause, No Fix' enforcement to prevent technical debt.

02Multi-component diagnostic instrumentation for tracing data across service boundaries.

03Scientific hypothesis testing using minimal variables to isolate failure points.

040 GitHub stars

05Architectural review triggers that stop infinite 'guess-and-check' loops after three failed attempts.

06Automated test-driven verification requirements for every implemented fix.

사용 사례

01Resolving intermittent test failures and race conditions in CI/CD pipelines.

02Debugging deep data-flow issues in microservices or multi-layered architectures.

03Identifying the source of performance regressions and build environment failures.