How does this skill handle multi-component system failures?

It uses a boundary-logging strategy where you must instrument the entry and exit points of every component (CI, API, DB) to gather evidence of exactly where the data flow breaks before attempting a fix.

When should I use the 4-phase framework?

Use it for any technical issue, including test failures, performance bottlenecks, and build errors. It is especially critical when you are under time pressure or when previous fix attempts have failed.

What happens if three or more fix attempts fail?

The skill instructs you to stop and question the fundamental architecture. If multiple fixes fail, it usually indicates a design flaw or a 'wrong architecture' rather than a simple code bug.

What is the Iron Law of this debugging skill?

The Iron Law states that no fixes can be proposed or implemented without first completing a full root cause investigation. This prevents 'masking' symptoms and ensures the underlying issue is actually resolved.

Does this skill work with other developer tools?

Yes, it specifically integrates with the 'trace' skill for backward data flow tracing and can be combined with TDD skills for implementing complex business logic fixes.

Systematic Debugging

Name: Systematic Debugging
Author: udecode

byudecode

•

1,127

セキュリティとテスト

Implements a rigorous four-phase protocol to identify root causes and ensure stable code fixes through scientific hypothesis testing.

概要

The Systematic Debugging skill transforms the debugging process from a series of guesses into a disciplined scientific workflow. By enforcing the 'Iron Law' of no fixes without root cause investigation, it guides developers through four mandatory phases: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation. This approach is specifically designed to eliminate 'thrashing'—where superficial fixes create new bugs—by requiring diagnostic instrumentation and data flow tracing. It is especially valuable for complex, multi-component systems where issues might span across CI/CD pipelines, APIs, and databases, and includes a built-in architectural review trigger if multiple fix attempts fail.

主な機能

Mandatory Phase-Gate Workflow: Enforces root cause proof before any code modification is permitted.
Pattern Analysis Protocol: Guides comparison between broken code and working references to isolate variables.
Multi-Layer Diagnostics: Provides structured patterns for instrumenting boundaries in complex systems.
1,127 GitHub stars
Architectural Health Check: Identifies systemic design flaws when traditional bug fixes consistently fail.
Scientific Hypothesis Testing: Focuses on minimal, single-variable changes to validate assumptions.

ユースケース

Debugging silent data corruption or flow issues across microservices and complex pipelines.
Stabilizing legacy codebases where manual 'quick fixes' frequently cause regressions.
Resolving persistent test failures or production bugs that resist simple troubleshooting.

概要

主な機能

Mandatory Phase-Gate Workflow: Enforces root cause proof before any code modification is permitted.
Pattern Analysis Protocol: Guides comparison between broken code and working references to isolate variables.
Multi-Layer Diagnostics: Provides structured patterns for instrumenting boundaries in complex systems.
1,127 GitHub stars
Architectural Health Check: Identifies systemic design flaws when traditional bug fixes consistently fail.
Scientific Hypothesis Testing: Focuses on minimal, single-variable changes to validate assumptions.

ユースケース

Debugging silent data corruption or flow issues across microservices and complex pipelines.
Stabilizing legacy codebases where manual 'quick fixes' frequently cause regressions.
Resolving persistent test failures or production bugs that resist simple troubleshooting.