What is the primary benefit of the Systematic Debugging skill?

It prevents 'thrashing' and temporary patches by enforcing a four-phase process that ensures a root cause is identified and understood before any code changes are proposed.

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

The skill includes a specific 'Iron Law' that mandates questioning the underlying architecture if three or more fix attempts fail, preventing endless patching of fundamentally flawed patterns.

When should I use the Systematic Debugging framework?

Use it for any technical issue including test failures, production bugs, build errors, or performance problems, especially when under time pressure or dealing with complex systems.

Does this skill help with debugging across different services?

Yes, it provides specific guidance for adding diagnostic instrumentation at component boundaries to trace data flow between workflows, build scripts, APIs, and databases.

How does this skill integrate with testing?

The final phase requires the creation of a minimal failing test case before the fix is implemented, ensuring the solution is verified and preventing future regressions.

Systematic Debugging

Name: Systematic Debugging
Author: penne-0505

bypenne-0505

セキュリティとテスト

Enforces a rigorous four-phase framework to identify root causes and implement verified fixes for complex software issues.

概要

Systematic Debugging is a specialized Claude Code skill designed to eliminate 'guess-and-check' development by mandating a strict investigative process. It guides developers through root cause investigation, pattern analysis, hypothesis testing, and rigorous implementation phases. By prioritizing deep understanding over quick patches, this skill prevents recurring bugs, reduces technical debt, and ensures that fixes address underlying architectural issues rather than just surface-level symptoms. It is particularly effective for multi-component systems where errors are buried deep within call stacks or across service boundaries.

主な機能

Four-phase debugging framework: Investigation, Analysis, Hypothesis, and Implementation
Backward tracing techniques for errors deep within the call stack
0 GitHub stars
Diagnostic instrumentation protocols for multi-component and distributed systems
Mandatory TDD integration to verify fixes with failing test cases
Architectural health checks triggered after multiple failed fix attempts

ユースケース

Resolving complex CI/CD pipeline failures through diagnostic logging and environment verification
Troubleshooting intermittent production bugs in multi-layered API architectures
Debugging unexpected behavior in legacy codebases by comparing against working reference patterns

概要

主な機能

Four-phase debugging framework: Investigation, Analysis, Hypothesis, and Implementation
Backward tracing techniques for errors deep within the call stack
0 GitHub stars
Diagnostic instrumentation protocols for multi-component and distributed systems
Mandatory TDD integration to verify fixes with failing test cases
Architectural health checks triggered after multiple failed fix attempts

ユースケース

Resolving complex CI/CD pipeline failures through diagnostic logging and environment verification
Troubleshooting intermittent production bugs in multi-layered API architectures
Debugging unexpected behavior in legacy codebases by comparing against working reference patterns