Is this process slower than traditional debugging?

While it requires more initial investigation, it is faster in the long run by reducing 'thrashing' (randomly trying fixes) and preventing the introduction of new bugs.

How does this skill handle multi-component system failures?

It mandates diagnostic instrumentation at component boundaries, logging data entry and exit points to identify exactly which layer (e.g., API, build script, or database) is failing.

Does this skill require Test-Driven Development (TDD)?

Yes, Phase 4 of the process requires creating a minimal failing test case before any fix is implemented to ensure the solution is verified and permanent.

What is the 'Iron Law' of this debugging skill?

The Iron Law dictates that no fixes should be proposed or attempted until a thorough root cause investigation (Phase 1) is completed and evidence of the failure point is gathered.

What happens if three fix attempts fail consecutively?

The process triggers a mandatory stop to question the fundamental architecture, shifting focus from fixing symptoms to discussing potential design flaws with the human partner.

Systematic Debugging

Name: Systematic Debugging
Author: claudiodearaujo

byclaudiodearaujo

0•

Seguridad y Pruebas

Implements a rigorous four-phase protocol to identify root causes and eliminate guess-and-check bug fixing.

This skill transforms Claude's troubleshooting approach by mandating a structured four-phase process: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation. It prevents the common pitfall of applying superficial patches by enforcing the 'Iron Law'—no fixes are proposed until the underlying cause is fully understood and evidenced. By requiring instrumentation, data flow tracing, and architectural questioning after repeated failures, it ensures that bugs are resolved permanently rather than masked by temporary workarounds.

Características Principales

01Diagnostic instrumentation for multi-component system troubleshooting

02Mandatory Root Cause Investigation phase before any fix is proposed

03Pattern analysis comparing broken code against working reference implementations

04Scientific hypothesis testing with minimal, single-variable changes

050 GitHub stars

06Automatic architectural re-evaluation trigger after three failed fix attempts

Casos de Uso

01Enforcing disciplined debugging workflows during high-pressure production incidents

02Resolving complex bugs in distributed systems where failures span multiple service boundaries

03Fixing persistent or intermittent test failures that have resisted previous quick-fix attempts

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add claudiodearaujo/izacenter systematic-debugging

For use in Claude.ai and ChatGPT

Características Principales

01Diagnostic instrumentation for multi-component system troubleshooting

02Mandatory Root Cause Investigation phase before any fix is proposed

03Pattern analysis comparing broken code against working reference implementations

04Scientific hypothesis testing with minimal, single-variable changes

050 GitHub stars

06Automatic architectural re-evaluation trigger after three failed fix attempts

Casos de Uso

01Enforcing disciplined debugging workflows during high-pressure production incidents

02Resolving complex bugs in distributed systems where failures span multiple service boundaries

03Fixing persistent or intermittent test failures that have resisted previous quick-fix attempts

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add claudiodearaujo/izacenter systematic-debugging

For use in Claude.ai and ChatGPT