When should I use Systematic Debugging?

It should be used for any technical issue, including test failures, performance problems, and build errors, especially when you are under time pressure and tempted to guess.

What happens if three consecutive fixes fail?

The skill triggers an architectural review. Instead of attempting a fourth fix, it mandates questioning the fundamental patterns and discussing the architecture with the human partner.

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

The Iron Law states that no fixes can be proposed until Phase 1 (Root Cause Investigation) is fully completed. This prevents shallow patches that mask underlying issues.

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

It uses diagnostic instrumentation at every component boundary (e.g., API to Database) to log entering/exiting data and environment state, revealing exactly where the flow breaks.

Systematic Debugging

Name: Systematic Debugging
Author: Tako3832

byTako3832

0•

보안 및 테스팅

Enforces a rigorous four-phase root cause analysis process to eliminate guesswork and permanent bug resolution.

The Systematic Debugging skill transforms Claude into a disciplined engineer that follows a strict 'Root Cause First' philosophy, preventing the cycle of random fixes and regression. By mandating a structured approach—spanning root cause investigation, pattern analysis, scientific hypothesis testing, and test-driven implementation—it ensures that every bug is fully understood before a single line of code is changed. This skill is indispensable for resolving complex multi-component failures, intermittent CI/CD issues, and deep architectural bugs where traditional trial-and-error debugging often fails.

주요 기능

01Multi-layer diagnostic instrumentation for complex system boundaries

02Scientific hypothesis testing using minimal, single-variable changes

03Structured pattern analysis comparing broken code against working references

04Architectural review triggers that prevent 'thrashing' after three failed attempts

050 GitHub stars

06Mandatory root cause investigation phase before any fix is proposed

사용 사례

01Resolving production bugs where data flow spans multiple services or layers

02Breaking out of 'fix-and-break' cycles where initial patches cause regressions

03Debugging intermittent test failures in complex CI/CD pipelines

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add tako3832/claude-skills systematic-debugging

For use in Claude.ai and ChatGPT

주요 기능

01Multi-layer diagnostic instrumentation for complex system boundaries

02Scientific hypothesis testing using minimal, single-variable changes

03Structured pattern analysis comparing broken code against working references

04Architectural review triggers that prevent 'thrashing' after three failed attempts

050 GitHub stars

06Mandatory root cause investigation phase before any fix is proposed

사용 사례

01Resolving production bugs where data flow spans multiple services or layers

02Breaking out of 'fix-and-break' cycles where initial patches cause regressions

03Debugging intermittent test failures in complex CI/CD pipelines

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add tako3832/claude-skills systematic-debugging

For use in Claude.ai and ChatGPT