What happens if a bug persists after multiple fix attempts?

If three or more fixes fail, the skill mandates an architectural review. This shifts the focus from fixing symptoms to questioning whether the underlying technical pattern is fundamentally sound.

Does this skill help with writing tests?

Yes, it integrates with TDD principles by requiring the creation of a failing test case in Phase 4 before any implementation of the fix begins.

What is the core principle of the Systematic Debugging skill?

The core principle is the 'Iron Law': No fixes are allowed without completing a root cause investigation first. This prevents symptom-masking and ensures long-term code stability.

How does this skill handle complex multi-component systems?

It implements diagnostic instrumentation at every component boundary, logging data entry and exit points to pinpoint exactly which layer of the stack is failing before investigating specific code.

Systematic Debugging

Name: Systematic Debugging
Author: claudiodearaujo

byclaudiodearaujo

0•

개발자 도구

Enforces a rigorous, four-phase diagnostic protocol to identify root causes and eliminate guesswork before applying code fixes.

The Systematic Debugging skill transforms how Claude approaches technical issues by mandating a disciplined diagnostic process. Instead of proposing 'quick fixes' that often mask underlying issues, this skill follows an 'Iron Law' that requires root cause investigation before any code changes are made. It guides the user through evidence gathering, pattern analysis, and minimal hypothesis testing, making it ideal for complex multi-component systems, intermittent production bugs, and issues where previous fix attempts have failed.

주요 기능

01Evidence-based logging requirements to prevent 'guess-and-check' thrashing

02Mandatory four-phase workflow: Root Cause, Pattern Analysis, Hypothesis, and Implementation

03Architectural red-flag detection that triggers fundamental reviews after three failed fix attempts

04Integration with Test-Driven Development (TDD) for verifiable bug resolution

050 GitHub stars

06Diagnostic instrumentation for tracing data flow across multi-component system boundaries

사용 사례

01Systematically identifying the source of regression bugs in large, unfamiliar codebases

02Debugging complex race conditions or data flow errors in distributed microservices

03Resolving persistent CI/CD or build failures that require environmental verification

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

주요 기능

01Evidence-based logging requirements to prevent 'guess-and-check' thrashing

02Mandatory four-phase workflow: Root Cause, Pattern Analysis, Hypothesis, and Implementation

03Architectural red-flag detection that triggers fundamental reviews after three failed fix attempts

04Integration with Test-Driven Development (TDD) for verifiable bug resolution

050 GitHub stars

06Diagnostic instrumentation for tracing data flow across multi-component system boundaries

사용 사례

01Systematically identifying the source of regression bugs in large, unfamiliar codebases

02Debugging complex race conditions or data flow errors in distributed microservices

03Resolving persistent CI/CD or build failures that require environmental verification

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