Does this skill replace manual testing?

No, it enhances it. It requires creating a reproducible failing test case (automated or script-based) as part of the implementation phase to verify the fix works and prevent regressions.

What happens if three consecutive fix attempts fail?

The skill instructs the developer to stop and question the underlying architecture. Multiple failed fixes often indicate a fundamental design flaw rather than a simple logic error.

When should I use the Systematic Debugging skill?

You should use it for any technical issue, but it is especially critical under time pressure, when 'obvious' fixes have failed, or when you are dealing with complex integration and build failures.

How does this skill help with multi-component systems?

It provides a structured logging protocol for component boundaries (e.g., API to Database), helping you identify exactly which layer the data flow breaks down before you start changing code.

What is the 'Iron Law' of systematic debugging?

The Iron Law dictates that no code fixes should be proposed or implemented until a thorough root cause investigation (Phase 1) is completed. This prevents masking symptoms instead of solving the actual problem.

Systematic Debugging

Name: Systematic Debugging
Author: claudiodearaujo

byclaudiodearaujo

0•

Security & Testing

Eliminates trial-and-error programming by enforcing a rigorous four-phase root cause analysis before applying code fixes.

Systematic Debugging is a specialized Claude Code skill designed to stop the cycle of 'quick patches' and 'guess-and-check' programming that often leads to technical debt. By implementing the 'Iron Law'—prohibiting fixes until a root cause is identified—this skill guides developers through systematic error reproduction, multi-component diagnostic instrumentation, pattern analysis, and minimal hypothesis testing. It is particularly effective for resolving complex test failures, production bugs, and architectural flaws where standard troubleshooting has failed, ensuring that every fix is intentional, verified, and permanent.

Key Features

01Integration with Test-Driven Development (TDD) to ensure every fix is backed by a failing test case.

02Architectural safety checks that trigger deep-dive reviews after three failed fix attempts.

03Mandatory four-phase debugging framework: Investigation, Pattern Analysis, Hypothesis, and Implementation.

04Root cause tracing techniques to track bad values back to their original source in the call stack.

050 GitHub stars

06Diagnostic instrumentation patterns for tracing data across multi-layer systems and CI/CD boundaries.

Use Cases

01Breaking out of 'thrashing' cycles where initial bug fixes create new, unexpected side effects.

02Debugging deep-seated data corruption issues across microservices or multi-component architectures.

03Resolving intermittent or 'flaky' test failures in complex integration environments.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add claudiodearaujo/sistema-de-narra-o-de-livro-front systematic-debugging

For use in Claude.ai and ChatGPT

Download Skill

Key Features

01Integration with Test-Driven Development (TDD) to ensure every fix is backed by a failing test case.

02Architectural safety checks that trigger deep-dive reviews after three failed fix attempts.

03Mandatory four-phase debugging framework: Investigation, Pattern Analysis, Hypothesis, and Implementation.

04Root cause tracing techniques to track bad values back to their original source in the call stack.

050 GitHub stars

06Diagnostic instrumentation patterns for tracing data across multi-layer systems and CI/CD boundaries.

Use Cases

01Breaking out of 'thrashing' cycles where initial bug fixes create new, unexpected side effects.

02Debugging deep-seated data corruption issues across microservices or multi-component architectures.

03Resolving intermittent or 'flaky' test failures in complex integration environments.