Does this skill provide specific tracing techniques?

Yes, it includes supporting techniques for backward call-stack tracing, defense-in-depth validation, and replacing fragile timeouts with condition-based waiting.

What is the 'Iron Law' of systematic debugging?

The Iron Law states that no fixes should be proposed or implemented until a full root cause investigation (Phase 1) has been completed and the underlying cause is understood.

What happens if three or more fix attempts fail?

The skill mandates a stop to regular debugging to question the fundamental architecture, as repeated failures usually indicate a flawed pattern rather than a simple bug.

Can I use this skill for simple, 'obvious' bugs?

Yes. Even simple bugs benefit from the process as it ensures the fix is verified with a test case and doesn't introduce unintended side effects.

How does this skill handle complex, multi-component systems?

It uses diagnostic instrumentation at every component boundary to log data entry/exit and environment state, allowing you to isolate exactly which layer is failing.

Systematic Debugging

Name: Systematic Debugging
Author: claudiodearaujo

byclaudiodearaujo

•

Seguridad y Pruebas

Implements a rigorous four-phase diagnostic framework to identify root causes and ensure stable, regression-free fixes.

Systematic Debugging is a specialized Claude Code skill designed to eliminate 'guess-and-check' programming by enforcing a disciplined diagnostic workflow. It guides the AI and developer through a structured process: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation. By strictly adhering to the 'Iron Law'—no fixes without root cause investigation—this skill helps solve complex issues in multi-component systems, reduces technical debt, and identifies when an issue requires architectural refactoring rather than simple patching.

Características Principales

011 GitHub stars

02Enforced four-phase diagnostic workflow (Investigation, Pattern, Hypothesis, Implementation)

03Root cause tracing for deep call stacks and data flow analysis

04Multi-layer diagnostic instrumentation for CI/CD, API, and database boundaries

05Evidence-based investigation protocols to prevent symptom-only patching

06Architectural verification trigger after three failed fix attempts

Casos de Uso

01Resolving intermittent production bugs or consistent test failures

02Debugging complex integrations across multiple system components

03Analyzing architectural flaws when multiple localized fixes fail to resolve an issue

What are Skills?·How to Install

Install with 🐟 Skill.Fish

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

For use in Claude.ai and ChatGPT

Download Skill