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

The Iron Law dictates that no fixes can be proposed until a full root cause investigation is completed, ensuring that symptoms aren't just masked by temporary patches.

What happens if three or more fix attempts fail?

The process identifies this as a red flag for an architectural problem, prompting a stop to the fixing cycle and a fundamental questioning of the system design with your human partner.

When is it best to use the Systematic Debugging skill?

It should be used for any technical issue including test failures, production bugs, and performance problems—especially when you feel tempted to apply a 'quick fix' under pressure.

How does this skill handle multi-component system failures?

It implements diagnostic instrumentation at every component boundary to log input/output data, allowing you to pinpoint exactly which layer the failure originates in.

Systematic Debugging

Name: Systematic Debugging
Author: astrosteveo

byastrosteveo

•

セキュリティとテスト

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

Systematic Debugging is a specialized Claude Code skill designed to eliminate 'guess-and-check' programming by mandating a root-cause-first approach. It guides developers through a disciplined workflow—Investigation, Pattern Analysis, Hypothesis Testing, and Implementation—to ensure that bugs are fully understood before they are patched. This skill is particularly valuable for complex multi-component systems where symptoms often mask deeper architectural issues, helping teams avoid 'thrashing' and the introduction of secondary bugs by requiring evidence-based diagnostics and minimal testing hypotheses.

主な機能

01Diagnostic instrumentation patterns for multi-layered and distributed systems

02Recursive data flow tracing to locate the origin of bad state

031 GitHub stars

04Scientific hypothesis testing to isolate variables during troubleshooting

05Mandatory Root Cause Investigation phase before any code modifications

06Architectural red-flag detection for recurring or persistent failures

ユースケース

01Resolving intermittent test failures or regressions in CI/CD pipelines

02Debugging complex integration issues across API, database, and frontend layers

03Troubleshooting production bugs where the immediate cause is obscured by environmental factors

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add astrosteveo/marketplace systematic-debugging

For use in Claude.ai and ChatGPT

Download Skill