Systematic Debugging

About

This skill transforms Claude into a disciplined troubleshooter by mandating a strict four-phase debugging protocol: root cause investigation, pattern analysis, hypothesis testing, and implementation. It eliminates the 'random fix' anti-pattern by requiring consistent reproduction, evidence gathering across multi-component systems, and data flow tracing. By following the 'Iron Law' of debugging—no fixes without root cause—this skill ensures that software issues are resolved permanently rather than just masked by superficial patches.

Key Features

• Diagnostic instrumentation patterns for debugging complex, multi-layer systems and CI/CD pipelines.
• Integration with Test-Driven Development (TDD) principles to verify fixes through failing test cases.
• Architectural safety valve that triggers a fundamental design review after three failed fix attempts.
• 0 GitHub stars
• Systematic data flow tracing techniques to identify the origin of bad state or logic.
• Strict four-phase debugging workflow: Investigation, Pattern Analysis, Hypothesis, and Implementation.

Use Cases

• Identifying the root cause of intermittent CI/CD pipeline failures and build environment issues.
• Resolving complex performance regressions or unexpected behavior in legacy codebases.
• Troubleshooting elusive bugs in distributed systems or microservice architectures.