How does it handle multi-component systems?

It guides the user to add diagnostic instrumentation at every component boundary to log data entry/exit and identify exactly where the system breaks.

When should I use this skill instead of just fixing a bug?

Use it for any technical issue, especially when under time pressure, when previous fixes have failed, or when you don't fully understand the unexpected behavior.

What is the 'Iron Law' of systematic debugging?

The Iron Law dictates that no fix should ever be proposed or implemented until a thorough root cause investigation is completed to prevent masking symptoms.

Does this skill require writing tests?

Yes, it integrates a 'Test First' approach, requiring a failing test case that reliably reproduces the issue before any implementation fix is applied.

How does the skill handle multiple failed fix attempts?

If three or more fixes fail, the skill forces a stop to question the underlying architecture, preventing 'fix thrashing' and identifying fundamental design flaws.

Systematic Debugging

Name: Systematic Debugging
Author: eyadsibai

byeyadsibai

0•

Security & Testing

Enforces a rigorous four-phase methodology to identify root causes and resolve technical issues without guess-and-check thrashing.

Systematic Debugging is a specialized Claude Code skill designed to eliminate the cycle of random fixes and quick patches that often mask underlying issues. By mandating an 'Iron Law' of root cause investigation before any fix is attempted, this skill guides developers through disciplined error analysis, evidence gathering in multi-component systems, and minimal hypothesis testing. It ensures that every solution is backed by a failing test case and provides a critical circuit breaker to question software architecture when repetitive fixes fail to resolve the core problem.

Key Features

01Mandatory root cause verification before proposing any code changes

02Architectural review trigger that activates after three failed fix attempts

03Diagnostic instrumentation patterns for tracing data flow across component boundaries

040 GitHub stars

05Strict four-phase debugging workflow: Root Cause, Pattern, Hypothesis, and Implementation

06Integrated Test-Driven Development (TDD) requirement for bug reproduction

Use Cases

01Managing high-pressure production emergencies where systematic analysis is faster than trial-and-error.

02Identifying elusive bugs in complex multi-component systems by tracing data flow and logging boundaries.

03Resolving persistent test failures or build breakages that have not responded to initial 'obvious' fixes.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add eyadsibai/ltk systematic-debugging

For use in Claude.ai and ChatGPT

Download Skill