Why does this skill prevent immediate code fixes?

The core principle is that fixes without a confirmed root cause often lead to technical debt and new bugs. By enforcing investigation first, the skill ensures long-term code stability.

Can this be used for multi-component systems?

Yes, it includes specific protocols for gathering evidence across component boundaries, such as between workflows, build scripts, and signing services.

Does this skill help with writing tests?

Absolutely. Phase 4 requires the creation of a failing test case before any fix is implemented, ensuring the bug is reproducible and the fix is verified.

How does the 'Three Fix Rule' work?

If three attempts to fix a bug fail, the skill stops the cycle and prompts the developer to question the underlying architecture rather than continuing to patch symptoms.

Systematic Debugging

Name: Systematic Debugging
Author: SwervoJake

bySwervoJake

0•

Security & Testing

Implements a rigorous four-phase root cause analysis process to eliminate guesswork and prevent recurring software bugs.

The Systematic Debugging skill provides a structured framework for diagnosing complex technical issues by enforcing a 'root cause first' methodology. It guides developers through evidence gathering, pattern analysis, and minimal hypothesis testing before any code fixes are applied, effectively eliminating the inefficient guess-and-check cycle. This approach is particularly valuable for multi-component systems and high-pressure environments where quick patches often lead to technical debt or regression bugs, ensuring that every fix is targeted and verified.

Key Features

01Mandatory four-phase debugging workflow from investigation to implementation

02Architectural safety checks that trigger after three failed fix attempts

030 GitHub stars

04Integration with Test-Driven Development for creating reproducible failing cases

05Diagnostic instrumentation for tracing data across multi-component boundaries

06Backward data flow tracing to identify the original source of bad values

Use Cases

01Debugging data flow issues in multi-layered API and database architectures

02Handling high-pressure production bugs where guessing could cause further outages

03Resolving intermittent test failures in complex CI/CD pipelines

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add swervojake/claaaude-studio systematic-debugging

For use in Claude.ai and ChatGPT

Key Features

01Mandatory four-phase debugging workflow from investigation to implementation

02Architectural safety checks that trigger after three failed fix attempts

030 GitHub stars

04Integration with Test-Driven Development for creating reproducible failing cases

05Diagnostic instrumentation for tracing data across multi-component boundaries

06Backward data flow tracing to identify the original source of bad values

Use Cases

01Debugging data flow issues in multi-layered API and database architectures

02Handling high-pressure production bugs where guessing could cause further outages

03Resolving intermittent test failures in complex CI/CD pipelines

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add swervojake/claaaude-studio systematic-debugging

For use in Claude.ai and ChatGPT