When is the best time to use the Systematic Debugging skill?

It should be used for any technical issue, but it is essential for complex bugs, multi-component system failures, or when 'obvious' fixes have already failed to resolve the problem.

What happens if a bug is not easily reproducible?

The skill guides you to gather more evidence through diagnostic instrumentation at component boundaries rather than guessing, ensuring you identify where the system state diverges.

Does this skill help with architectural problems?

Yes. If three or more fixes fail to resolve the issue, the framework triggers a phase to question the fundamental architecture rather than continuing to apply failing patches.

How does this skill differ from standard debugging?

Standard debugging often involves trial and error. This skill enforces a scientific 4-phase process (Investigation, Analysis, Hypothesis, Implementation) that strictly forbids proposing a fix until the root cause is proven.

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

The Iron Law is: 'No fixes without root cause investigation first.' This prevents masking underlying issues with superficial patches that might cause regressions.

Systematic Debugging

Name: Systematic Debugging
Author: penne-0505

bypenne-0505

0•

セキュリティとテスト

Applies a rigorous four-phase framework to identify root causes and implement stable fixes for complex software bugs.

This skill transforms Claude's debugging process from 'guess-and-check' into a scientific methodology. By enforcing a strict four-phase workflow—Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation—it ensures that developers never apply a patch without fully understanding the underlying issue. It is particularly effective for multi-component systems, elusive test failures, and scenarios where initial fix attempts have failed, prompting a critical review of the system architecture when necessary. By following this iron-clad process, developers reduce thrashing and ensure that every fix addresses the source rather than just the symptoms.

主な機能

01Scientific hypothesis testing to isolate variables and verify theories

02Automatic architectural review triggers after three failed fix attempts

030 GitHub stars

04Mandatory root cause investigation phase before any code modifications

05Diagnostic instrumentation patterns for multi-component system boundaries

06Comparative pattern analysis against working reference implementations

ユースケース

01Isolating data flow errors across multiple API, service, and database layers

02Troubleshooting intermittent failures in complex CI/CD pipelines and build scripts

03Resolving recurring production bugs that have resisted previous patch attempts

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add penne-0505/docs_driven_dev_template debug

For use in Claude.ai and ChatGPT

Download Skill