When should I question the system architecture?

According to the skill's 'Iron Law,' if three or more fix attempts fail, you should stop and evaluate if the underlying architecture is fundamentally flawed rather than the specific code block.

How does this skill help speed up debugging?

While it requires more initial analysis, it prevents 'thrashing' and 'guess-and-check' cycles, which often lead to regression bugs and wasted time.

Can I use this for production emergencies?

Yes, it is specifically designed to keep debugging disciplined under pressure, ensuring that emergency fixes address the actual problem rather than just masking symptoms.

What happens if I can't find a root cause?

The skill provides a framework for environmental and external investigation, helping you document evidence and implement robust error handling or monitoring instead of guessing.

Systematic Debugging

Name: Systematic Debugging
Author: bgrober

bybgrober

•

Security & Testing

Enforces a rigorous four-phase scientific process to identify root causes and implement stable fixes for technical issues.

The Systematic Debugging skill transforms the debugging workflow from a trial-and-error approach into a disciplined, evidence-based methodology. It guides Claude through four distinct phases: investigating the root cause through evidence gathering, analyzing patterns against working code, forming and testing specific hypotheses, and implementing verified fixes using test-driven development. By preventing 'quick patches' and requiring diagnostic instrumentation for multi-component systems, this skill reduces debugging time, prevents the introduction of new bugs, and signals when recurring failures indicate a need for architectural changes rather than simple code fixes.

Key Features

01Strict Root Cause Investigation phase before proposing any code changes

02Hypothesis-driven testing to isolate variables during troubleshooting

03Diagnostic instrumentation for evidence gathering in multi-layer systems

04Mandatory test-driven verification to ensure fix stability and prevent regressions

05Comparative pattern analysis against known working reference implementations

061 GitHub stars

Use Cases

01Debugging multi-component systems where data flow is obscured between layers

02Breaking cycles of 'fix-thrashing' when multiple previous attempts have failed

03Troubleshooting intermittent test failures or production bugs in complex stacks

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add bgrober/indie-stack systematic-debugging

For use in Claude.ai and ChatGPT

Download Skill