Does this skill integrate with other PopKit tools?

Yes, it seamlessly transitions to the Test-Driven Development (TDD) and Root Cause Tracing skills to implement and verify fixes once the cause is identified.

What is the 'Iron Law' of this debugging skill?

The Iron Law mandates that no fixes be proposed or applied until a thorough root cause investigation (Phase 1) is completed to avoid fixing symptoms instead of the actual problem.

When should I use this skill instead of a quick fix?

Use this skill for issues spanning multiple components, recurring bugs, or when standard debugging attempts have failed to resolve the problem.

How does it handle flaky tests?

The skill includes a specialized check that runs failing tests multiple times to determine if the failure is consistent or intermittent, ensuring flaky tests are fixed before debugging the application logic.

Systematic Debugging

Name: Systematic Debugging
Author: jrc1883

byjrc1883

Seguridad y Pruebas

Implements a rigorous four-phase framework that enforces root cause investigation before applying fixes to complex bugs or test failures.

Acerca de

The Systematic Debugging skill provides a disciplined approach to software troubleshooting by moving beyond 'guess-and-check' methods. It guides Claude through a structured workflow consisting of initial triage, pattern analysis, hypothesis testing, and validated implementation. By mandating that a root cause be identified and verified before any code is modified, it eliminates the risk of symptom-only patches and regressions. This skill is ideal for intermittent test flakiness, deep architectural issues, and multi-component system failures where the source of the error is not immediately obvious.

Características Principales

0 GitHub stars
Enforced four-phase debugging workflow
Automated test flakiness detection and resolution
Integrated diagnostic instrumentation for multi-component systems
Validation of fixes via Test-Driven Development (TDD) patterns
Pattern analysis against working code references

Casos de Uso

Debugging complex regressions that span across multiple services or components
Resolving intermittent CI/CD test failures by identifying flakiness
Investigating performance degradation using a hypothesis-driven approach

Acerca de

Características Principales

0 GitHub stars
Enforced four-phase debugging workflow
Automated test flakiness detection and resolution
Integrated diagnostic instrumentation for multi-component systems
Validation of fixes via Test-Driven Development (TDD) patterns
Pattern analysis against working code references

Casos de Uso

Debugging complex regressions that span across multiple services or components
Resolving intermittent CI/CD test failures by identifying flakiness
Investigating performance degradation using a hypothesis-driven approach