Why does the skill suggest questioning the architecture after three failed fixes?

If three different fix attempts fail, it often indicates a fundamental design flaw or high coupling rather than a simple bug, requiring a higher-level architectural discussion.

Does this skill require writing tests?

Yes, Phase 4 of the process mandates creating a failing test case to reproduce the bug before implementing the final fix to ensure it remains resolved.

What is the primary goal of the Systematic Debugging skill?

The primary goal is to ensure the actual root cause of an issue is identified through evidence before any code changes are proposed, preventing 'symptom-masking' and wasted effort.

When should I use this skill instead of a quick fix?

It should be used for any technical issue, especially under time pressure, when the cause isn't immediately obvious, or after multiple failed attempts to fix a bug.

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

It provides specific instrumentation strategies to log data at every component boundary (e.g., Workflow to Build Script), allowing you to pinpoint exactly where the failure occurs.

Systematic Debugging

Name: Systematic Debugging
Author: flosrn

byflosrn

0•

보안 및 테스팅

Implements a rigorous four-phase protocol to identify root causes and eliminate bugs through evidence-based troubleshooting rather than trial and error.

The Systematic Debugging skill enforces a disciplined workflow designed to stop the 'guess-and-check' cycle that leads to technical debt and regression. By mandating a strict sequence of root cause investigation, pattern analysis, hypothesis testing, and test-driven implementation, it ensures that Claude identifies why a failure is happening before proposing code changes. This is particularly valuable for complex multi-component systems where data flow is obscured, and it includes a unique 'architectural pivot' trigger that alerts developers when a problem requires a structural redesign rather than a simple patch.

주요 기능

01Strict four-phase debugging protocol to prevent symptom-only fixes

02Architectural review trigger activated after three failed fix attempts

030 GitHub stars

04Diagnostic instrumentation strategies for multi-layer and CI/CD environments

05Mandatory test-driven verification to ensure permanent bug resolution

06Backward data-flow tracing techniques to locate original bug triggers

사용 사례

01Resolving recurring bugs where previous quick-fix attempts have failed or caused regressions

02Troubleshooting elusive failures in complex CI/CD pipelines or build systems

03Debugging data flow issues across API, service, and database boundaries

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add flosrn/.claude systematic-debugging

For use in Claude.ai and ChatGPT

주요 기능

01Strict four-phase debugging protocol to prevent symptom-only fixes

02Architectural review trigger activated after three failed fix attempts

030 GitHub stars

04Diagnostic instrumentation strategies for multi-layer and CI/CD environments

05Mandatory test-driven verification to ensure permanent bug resolution

06Backward data-flow tracing techniques to locate original bug triggers

사용 사례

01Resolving recurring bugs where previous quick-fix attempts have failed or caused regressions

02Troubleshooting elusive failures in complex CI/CD pipelines or build systems

03Debugging data flow issues across API, service, and database boundaries