How does this skill handle complex, multi-component systems?

It uses diagnostic instrumentation at component boundaries to log data entry/exit, verify environment configurations, and pinpoint exactly where the failure occurs before attempting a fix.

Does this skill require specific testing frameworks?

No, it is framework-agnostic. It integrates with Test-Driven Development (TDD) by requiring the creation of a failing reproduction (automated test or script) before any fix is implemented.

What happens if multiple fix attempts fail?

If three or more fixes fail, the skill stops the debugging process to trigger an architectural review, helping determine if the issue is a fundamental design flaw rather than a simple bug.

What is the 'Iron Law' of this skill?

The Iron Law mandates that no code fixes should be proposed or implemented until a thorough root cause investigation has been completed and the failure is fully understood.

Can I use this for simple bugs or just complex ones?

It is recommended for all technical issues. While it handles complex problems, the process is fast for simple bugs and prevents the common mistake of applying superficial patches.

Systematic Debugging Framework

Name: Systematic Debugging Framework
Author: hanibalsk

byhanibalsk

セキュリティとテスト

Implements a rigorous four-phase debugging methodology to identify root causes and ensure reliable software fixes.

概要

This skill equips Claude with a structured debugging protocol designed to eliminate inefficient 'guess-and-check' workflows. It enforces a strict 'Iron Law' that prevents premature code changes, requiring comprehensive root cause investigation, pattern analysis, and minimal hypothesis testing before any implementation occurs. By following these structured phases, the skill helps developers solve complex bugs in multi-component systems, reduces the introduction of new regressions, and identifies when persistent failures indicate deeper architectural issues rather than simple code errors.

主な機能

Integration with TDD principles and backward data-flow tracing
Four-phase framework: Root Cause, Pattern Analysis, Hypothesis, and Implementation
Strict 'No Fix without Root Cause' enforcement to prevent superficial patches
Multi-component diagnostic instrumentation for tracing data across system boundaries
Architectural red-flag detection after repeated failed fix attempts
0 GitHub stars

ユースケース

Debugging data integrity issues across microservices or multi-layered APIs
Investigating build and deployment failures that lack clear error messages
Resolving intermittent test failures or production bugs in complex environments

概要

主な機能

Integration with TDD principles and backward data-flow tracing
Four-phase framework: Root Cause, Pattern Analysis, Hypothesis, and Implementation
Strict 'No Fix without Root Cause' enforcement to prevent superficial patches
Multi-component diagnostic instrumentation for tracing data across system boundaries
Architectural red-flag detection after repeated failed fix attempts
0 GitHub stars

ユースケース

Debugging data integrity issues across microservices or multi-layered APIs
Investigating build and deployment failures that lack clear error messages
Resolving intermittent test failures or production bugs in complex environments