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

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

What happens if three or more fix attempts fail?

If 3+ fixes fail, the process requires you to stop and question the underlying architecture rather than continuing to fix symptoms, as this pattern usually indicates a fundamental design flaw.

How does this skill handle failures in multi-component systems?

It adds diagnostic instrumentation at EACH component boundary to log data entry and exit, identifying exactly which layer is failing before investigating the specific code.

When should I use the Systematic Debugging skill?

Use it for any technical issue including test failures, production bugs, performance problems, or especially when you feel the urge to apply a 'quick fix' without understanding the problem.

Systematic Debugging

Name: Systematic Debugging
Author: zoosewu

byzoosewu

0•

Security & Testing

Implements a rigorous, four-phase debugging methodology to identify root causes and eliminate trial-and-error bug fixing.

The Systematic Debugging skill transforms Claude into a disciplined engineer that prioritizes root-cause analysis over quick patches. By enforcing a structured 'Iron Law' of investigation, it guides users through evidence gathering, pattern analysis, hypothesis testing, and verified implementation. This approach prevents 'thrashing'—where multiple failed fixes introduce new bugs—and ensures that complex issues in multi-component systems are solved at their source rather than masked by symptoms, significantly reducing the time spent on repetitive rework.

Key Features

01Automated reproduction steps and consistency verification

020 GitHub stars

03Data flow tracing and backward call-stack analysis techniques

04Four-phase framework: Investigation, Pattern, Hypothesis, and Implementation

05Architectural sanity checks triggered after repeated fix failures

06Multi-component diagnostic instrumentation for boundary-layer logging

Use Cases

01Standardizing team debugging processes to prevent technical debt from quick patches

02Resolving intermittent CI/CD build failures or environment-specific bugs

03Debugging complex data flow issues across microservices and databases

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add zoosewu/mackup systematic-debugging

For use in Claude.ai and ChatGPT

Download Skill