How does this skill handle complex system boundaries?

It uses diagnostic instrumentation to log data as it enters and exits component boundaries, helping identify exactly which layer (e.g., API, database, or build script) is failing.

What happens if multiple fix attempts fail?

If three or more fix attempts fail, the skill triggers a 'Phase 4.5' review to question the underlying architecture, preventing the developer from continuing to treat symptoms of a fundamentally flawed design.

Can this skill be used with Test-Driven Development (TDD)?

Yes, Phase 4 of the process requires creating a failing test case before implementing any fix, making it a perfect companion for TDD workflows.

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

The Iron Law mandates that no code fixes are proposed or implemented until a thorough root cause investigation (Phase 1) is completed and the source of the error is verified.

Systematic Debugging

Name: Systematic Debugging
Author: pedropaulovc

bypedropaulovc

0•

Seguridad y Pruebas

Implements a rigorous, four-phase debugging protocol to identify root causes and prevent regressions before applying code fixes.

The Systematic Debugging skill transforms Claude into a disciplined troubleshooter that adheres to the 'Iron Law': no fixes without root cause investigation. By guiding the AI through structured phases—investigation, pattern analysis, hypothesis testing, and implementation—it prevents time-wasting 'guess-and-check' cycles and ensures fixes address the actual source of the problem rather than just the symptoms. It is especially effective for complex multi-component systems, intermittent failures, and cases where previous fix attempts have failed, prompting deep architectural reviews when necessary.

Características Principales

01Enforces a strict 'Root Cause First' workflow before any code modification

02Requires minimal hypothesis testing and mandatory failing test case creation

030 GitHub stars

04Provides diagnostic instrumentation for multi-component system boundaries

05Triggers architectural questioning after three consecutive failed fix attempts

06Utilizes backward data flow tracing to locate original bug triggers

Casos de Uso

01Debugging intermittent production errors or complex CI/CD pipeline failures

02Resolving deep-seated data flow issues in multi-layered microservices

03Preventing 'fix thrashing' during high-pressure emergency bug resolution

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add pedropaulovc/personal-marketplace systematic-debugging

For use in Claude.ai and ChatGPT

Download Skill