What is the Iron Law of this debugging skill?

The Iron Law mandates that no fixes should be proposed or implemented until a thorough Phase 1 Root Cause Investigation is completed to ensure the source of the problem is understood.

How does this skill handle bugs that are hard to reproduce?

It guides the user through gathering diagnostic data, checking recent git diffs, and adding instrumentation at component boundaries to gather evidence where the system breaks.

Can this skill be used for build failures or performance issues?

Yes, the systematic approach is designed for any technical issue, including performance bottlenecks, build failures, and unexpected environment-specific behavior.

What happens if a bug isn't fixed after three attempts?

The skill invokes a mandatory stop to question the fundamental architecture, as repeated failures often indicate an underlying problem with shared state or system coupling rather than a simple bug.

Does this skill help with writing tests?

Yes, Phase 4 of the process requires creating a minimal failing test case to reproduce the bug before a single fix is implemented, ensuring the solution is verified and prevents regressions.

Systematic Code Debugging

Name: Systematic Code Debugging
Author: srnnkls

bysrnnkls

セキュリティとテスト

Implements a disciplined, four-phase debugging methodology to identify root causes and eliminate recurring software bugs.

概要

The Systematic Code Debugging skill enforces a rigorous 'Root Cause First' approach to troubleshooting technical issues, ranging from production bugs to test failures. By moving through distinct phases—Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation—it prevents 'guess-and-check' coding and ensures that fixes address the source of a problem rather than just its symptoms. This skill is particularly valuable for complex, multi-component systems where architectural issues often masquerade as simple errors, providing a structured framework to trace data flow backward through the call chain.

主な機能

Architectural 'Stop Rule' triggered after three failed fix attempts to re-evaluate system design
Mandatory root cause investigation phase before any code modifications
Pattern analysis to compare failing code against known working reference implementations
0 GitHub stars
Backwards data flow tracing to locate the original trigger of deep-stack errors
Integrated verification workflow requiring failing test cases before implementing fixes

ユースケース

Debugging production emergencies where systematic analysis is faster than trial-and-error
Resolving persistent test failures that surface deep within complex call stacks
Tracing data corruption issues in multi-component systems with heavy coupling

概要

主な機能

Architectural 'Stop Rule' triggered after three failed fix attempts to re-evaluate system design
Mandatory root cause investigation phase before any code modifications
Pattern analysis to compare failing code against known working reference implementations
0 GitHub stars
Backwards data flow tracing to locate the original trigger of deep-stack errors
Integrated verification workflow requiring failing test cases before implementing fixes

ユースケース

Debugging production emergencies where systematic analysis is faster than trial-and-error
Resolving persistent test failures that surface deep within complex call stacks
Tracing data corruption issues in multi-component systems with heavy coupling