How does this skill prevent bug regressions?

The skill enforces a TDD (Test-Driven Development) workflow where a failing test must be created before a fix is implemented. It then requires the addition of permanent regression tests to ensure the bug never returns.

What is the 5 Whys technique used in this skill?

The 5 Whys is a systematic interrogation technique used to explore the cause-and-effect relationships underlying a problem. By asking 'why' repeatedly, Claude can drill down past symptoms to find the actual root cause of a failure.

Does this skill work for intermittent bugs?

Yes, it provides specific strategies for identifying the specific timing, data states, and environmental conditions required to transform intermittent failures into 100% reliable reproductions.

What is the purpose of the error-log.md file?

The error-log.md acts as an auditable record of all investigated issues. It stores the error ID, root cause analysis, fix details, and prevention steps, serving as a historical reference for the entire development team.

Systematic Debugging Phase

Name: Systematic Debugging Phase
Author: marcusgoll

bymarcusgoll

•

보안 및 테스팅

Implements a rigorous debugging workflow to identify root causes, classify errors, and ensure permanent fixes through regression testing and documentation.

소개

The Systematic Debugging Phase skill transforms troubleshooting from ad-hoc guesswork into a disciplined engineering process. By leveraging techniques like the '5 Whys' root cause analysis and standardized error classification, it helps Claude identify the underlying source of failures rather than just patching symptoms. The skill enforces a test-driven approach to bug fixing, ensuring that every resolution is backed by a regression test and documented in a centralized, auditable error log to prevent the same issues from resurfacing.

주요 기능

Test-driven bug resolution with mandatory regression testing
Root cause analysis using the 5 Whys interrogation technique
Centralized error auditing via a searchable error-log.md system
Repeatable strategies for reproducing intermittent and complex failures
Standardized error classification by type, severity, and component
18 GitHub stars

사용 사례

Building a searchable knowledge base of technical debt and system errors
Ensuring production-grade reliability through rigorous regression-proof fixes
Investigating complex race conditions or intermittent integration timeouts

소개

주요 기능

Test-driven bug resolution with mandatory regression testing
Root cause analysis using the 5 Whys interrogation technique
Centralized error auditing via a searchable error-log.md system
Repeatable strategies for reproducing intermittent and complex failures
Standardized error classification by type, severity, and component
18 GitHub stars

사용 사례

Building a searchable knowledge base of technical debt and system errors
Ensuring production-grade reliability through rigorous regression-proof fixes
Investigating complex race conditions or intermittent integration timeouts