Is this framework suitable for urgent production hotfixes?

Yes. It is specifically designed for high-pressure situations where the temptation to guess is high, preventing the 'fix-and-break' cycle common in emergencies.

What is the Iron Law of Systematic Debugging?

The Iron Law states that no fixes can be proposed or implemented until Phase 1: Root Cause Investigation is completed and the actual source of the problem is understood.

Does it integrate with other developer workflows?

Yes, it is designed to work alongside test-driven development (TDD) and root-cause-tracing techniques to provide a comprehensive quality assurance workflow.

How does this skill prevent new bugs from being created?

By forcing a data-driven investigation and requiring a failing test case before any fix is applied, it ensures that changes are targeted and verified.

What should I do if a fix fails after three attempts?

The skill advises stopping the process to question the underlying architecture and discuss potential refactoring with the user rather than continuing with incremental patches.

Systematic Debugging Framework

Name: Systematic Debugging Framework
Author: timequity

bytimequity

0•

Security & Testing

Enforces a disciplined four-phase engineering framework to identify and resolve software bugs by uncovering root causes before attempting fixes.

The Systematic Debugging skill for Claude Code replaces trial-and-error troubleshooting with a rigorous, evidence-based methodology. It operates under the 'Iron Law' that no fix should be proposed until a root cause is fully investigated and understood. By guiding developers through Phase 1: Root Cause Investigation, Phase 2: Pattern Analysis, Phase 3: Hypothesis Testing, and Phase 4: Implementation, the skill ensures that bugs are resolved at their source rather than being masked by symptomatic patches. This approach is particularly effective for complex systems, intermittent failures, and high-pressure production emergencies where guesswork leads to regressions.

Key Features

01Strict four-phase debugging workflow to prevent premature and incorrect fixes

02Pattern analysis tools to compare broken logic against working reference code

03Test-driven implementation requirements to ensure long-term bug resolution

040 GitHub stars

05Evidence-based investigation protocols including data flow tracing and error analysis

06Single-variable hypothesis testing to isolate variables and verify theories

Use Cases

01Debugging multi-component systems where errors propagate across boundaries

02Investigating intermittent test failures and environmental configuration issues

03Resolving complex production bugs where previous 'quick fixes' have failed

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add timequity/plugins systematic-debugging

For use in Claude.ai and ChatGPT

Download Skill