Does this skill require writing tests?

Yes. Phase 4 requires the creation of a failing test case that reproduces the bug before any implementation changes are made, ensuring the fix is verified and permanent.

How does this skill handle complex multi-component systems?

It uses diagnostic instrumentation at every component boundary to log data entry and exit, allowing it to pinpoint exactly which layer is failing before investigating that specific component.

What happens if a bug persists after multiple fix attempts?

If three or more fixes fail, the skill triggers an architectural review. This helps determine if the issue is a fundamental design flaw rather than a simple bug that can be patched.

What is the primary rule of the Systematic Debugging skill?

The core principle is the 'Iron Law': no fixes may be proposed or attempted until a full Phase 1 Root Cause Investigation is completed and the source of the issue is understood.

Why use this process for simple bugs?

Even simple bugs have root causes. Following a systematic process ensures that even 'quick' fixes are accurate, preventing rework and the introduction of secondary bugs.

Systematic Debugging

Name: Systematic Debugging
Author: julianromli

byjulianromli

•

101

•

開発者ツール

Enforces a rigorous, four-phase root cause analysis process to eliminate guesswork and ensure stable, long-term bug fixes.

The Systematic Debugging skill transforms how Claude approaches technical issues by mandating a strict 'root cause first' methodology. Instead of applying symptomatic patches, it guides the AI through structured evidence gathering, pattern analysis, and minimal hypothesis testing. By requiring a consistent reproduction and a failing test case before any code is modified, this skill ensures higher first-time fix rates and prevents architectural instability, especially in complex multi-layered systems where bugs often hide across component boundaries.

主な機能

01Backward data flow tracing to identify the true origin of logic errors

02101 GitHub stars

03Multi-component diagnostic instrumentation for tracing data across service boundaries

04Mandatory Test-Driven Development (TDD) integration for fix verification

05Structured four-phase debugging workflow (Investigation, Pattern, Hypothesis, Implementation)

06Automated architectural health checks triggered after repeated failed fix attempts

ユースケース

01Identifying environmental or configuration propagation issues in multi-component architectures

02Debugging intermittent failures in complex CI/CD pipelines or distributed systems

03Conducting root cause analysis for production bugs when previous quick fixes have failed

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