What happens if three different fixes fail to solve the problem?

The skill triggers an architectural review protocol. This signals that the issue may be a fundamental design flaw or an incorrect pattern rather than a simple logic error.

Why does this skill prevent me from proposing a fix immediately?

The skill enforces the 'Iron Law' of debugging: no fixes without root cause. This prevents 'thrashing' where quick patches mask underlying issues or create new bugs elsewhere in the system.

How does the 4-phase framework improve my workflow?

It moves you through Investigation, Pattern Analysis, Hypothesis, and Implementation, ensuring you solve the problem once and for all rather than guessing, which saves time in the long run.

Can I use this for multi-component systems like CI/CD or APIs?

Yes, it includes specific protocols for adding diagnostic instrumentation at component boundaries to see exactly where data flow breaks in complex pipelines.

Does this skill require specific testing tools?

It is framework-agnostic but requires creating a failing test case—either through an existing framework or a standalone script—before any fix is applied.

Systematic Debugging

Name: Systematic Debugging
Author: chriscarterux

bychriscarterux

•

セキュリティとテスト

Implements a disciplined, four-phase framework to identify root causes and eliminate bugs without trial-and-error thrashing.

This skill transforms Claude into a disciplined debugging partner by enforcing a strict 'Root Cause First' policy. It guides the AI through four essential phases: investigating evidence, analyzing patterns, testing hypotheses, and implementing verified fixes. By preventing premature code changes and emphasizing diagnostic instrumentation, this skill reduces the time spent on guess-and-check debugging and ensures that fixes address underlying architectural issues rather than just surface-level symptoms. It is particularly effective for complex, multi-layered systems where the source of an error is not immediately obvious.

主な機能

013 GitHub stars

02Mandatory root cause investigation protocol before any code modification

03Systematic data flow tracing to identify the origin of corrupted state

04Multi-component diagnostic instrumentation for tracing data across system boundaries

05Architectural escalation protocol triggered after three failed fix attempts

06Hypothesis-driven testing to isolate variables and verify assumptions

ユースケース

01Debugging intermittent test failures or production bugs with no clear origin

02Preventing 'fix-and-break' cycles in legacy codebases where changes have side effects

03Resolving complex integration issues between multiple services or CI/CD layers

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add chriscarterux/chris-claude-stack systematic-debugging

For use in Claude.ai and ChatGPT

主な機能

013 GitHub stars

02Mandatory root cause investigation protocol before any code modification

03Systematic data flow tracing to identify the origin of corrupted state

04Multi-component diagnostic instrumentation for tracing data across system boundaries

05Architectural escalation protocol triggered after three failed fix attempts

06Hypothesis-driven testing to isolate variables and verify assumptions

ユースケース

01Debugging intermittent test failures or production bugs with no clear origin

02Preventing 'fix-and-break' cycles in legacy codebases where changes have side effects

03Resolving complex integration issues between multiple services or CI/CD layers