What happens if three fix attempts fail?

The skill triggers an architectural review. This acknowledges that the pattern being used might be fundamentally flawed, preventing further wasted effort on symptom-level fixes.

How does it handle multi-component systems?

It adds diagnostic instrumentation at every component boundary (e.g., Workflow to Build script) to gather evidence and pinpoint exactly where data corruption or failures occur.

Is this skill compatible with Test-Driven Development (TDD)?

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

Why can't I just apply a quick fix with this skill?

The skill follows the 'Iron Law': no fixes without a root cause investigation. This prevents masking underlying issues and introducing new bugs that result from partial understanding.

Systematic Debugging

Name: Systematic Debugging
Author: clsandoval

byclsandoval

0•

セキュリティとテスト

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

Systematic Debugging is a specialized Claude Code skill designed to eliminate guess-and-check coding by enforcing a disciplined diagnostic workflow. It guides developers through a mandatory root cause investigation phase, multi-component data tracing, and pattern analysis before any code changes are proposed. This skill is particularly valuable for complex monorepos and multi-layer systems where "quick fixes" often mask deeper architectural issues, ensuring that every bug is resolved at its source with verified evidence and automated test cases. By following this scientific approach, users can reduce time spent thrashing and significantly increase the stability of their codebase.

主な機能

010 GitHub stars

02Mandatory Phase 1: Root cause investigation before any fix proposal

03Architectural review triggers after repeated failed fix attempts

04Scientific hypothesis testing with minimal variable changes

05Multi-component diagnostic instrumentation and data flow tracing

06Pattern analysis against working reference implementations

ユースケース

01Standardizing debugging methodology across a team to reduce thrashing and technical debt

02Resolving intermittent failures in complex CI/CD pipelines or multi-component systems

03Debugging production bugs where the error message doesn't reveal the true source

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add clsandoval/monorepo systematic-debugging

For use in Claude.ai and ChatGPT

主な機能

010 GitHub stars

02Mandatory Phase 1: Root cause investigation before any fix proposal

03Architectural review triggers after repeated failed fix attempts

04Scientific hypothesis testing with minimal variable changes

05Multi-component diagnostic instrumentation and data flow tracing

06Pattern analysis against working reference implementations

ユースケース

01Standardizing debugging methodology across a team to reduce thrashing and technical debt

02Resolving intermittent failures in complex CI/CD pipelines or multi-component systems

03Debugging production bugs where the error message doesn't reveal the true source