What happens if three or more fixes fail?

The skill triggers an architectural review, prompting the user to question fundamental design assumptions rather than continuing to patch symptoms.

What are the four phases of this debugging process?

The process includes Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and finally, Implementation with verification.

Does this skill help with intermittent or flaky tests?

Yes, it provides specific strategies for consistent reproduction and diagnostic instrumentation to capture data from non-deterministic failures.

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

Use it for all technical issues, especially when under time pressure, after multiple failed fix attempts, or when dealing with complex multi-component systems.

How does systematic debugging differ from standard AI bug fixing?

Standard AI often guesses fixes based on symptoms; this skill mandates evidence gathering and root cause identification before any code changes are suggested.

Systematic Debugging Strategy

Name: Systematic Debugging Strategy
Author: julianromli

byjulianromli

•

101

•

セキュリティとテスト

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

The Systematic Debugging skill transforms Claude's troubleshooting approach from 'guess-and-check' to a scientific, root-cause-first methodology. It enforces a strict workflow of reproduction, evidence gathering through diagnostic instrumentation, and hypothesis testing before any code changes are proposed. This skill is particularly valuable for resolving intermittent failures in distributed systems, deep architectural flaws, and regressions where simple patches have previously failed, ensuring long-term code stability rather than temporary symptom masking.

主な機能

01Architectural review triggers after repeated failed fix attempts

02Multi-component diagnostic instrumentation for complex system tracing

03Data flow analysis to track bugs back to their original trigger points

04Mandatory root cause investigation before proposing any code fixes

05Scientific hypothesis testing to verify fixes with minimal changes

06101 GitHub stars

ユースケース

01Resolving intermittent test failures or production bugs with no obvious cause

02Debugging complex interactions between microservices or multi-layered pipelines

03Preventing 'bug-fixing thrash' where new patches introduce unexpected regressions

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add julianromli/opencode-template systematic-debugging

For use in Claude.ai and ChatGPT

Download Skill