How does this skill prevent trial-and-error fixes?

The skill uses file-level permissions to block edits to production code during the reproduction and hypothesis phases, forcing the user to prove they understand the bug first.

What are adversary gates?

Adversary gates are checkpoints where the workflow challenges the agent's reasoning, asking for alternative explanations to ensure the diagnosis is accurate and not coincidental.

Can I use this for any programming language?

Yes, while the core scripts are Python-based, the logic and file-restriction patterns can be applied to any codebase with standard testing structures.

What happens if a prediction fails during the PROVE phase?

The workflow triggers 'kickback logic,' moving the process back to the HYPOTHESIZE phase to ensure the root cause is re-evaluated rather than applying a guessed fix.

What is a systematic debug workflow?

It is a structured approach to software debugging that requires identifying the bug, creating a reproduction case, and proving a hypothesis before attempting a fix.

Systematic Debug Workflow

Name: Systematic Debug Workflow
Author: c-daly

byc-daly

보안 및 테스팅

Enforces a rigorous, multi-phase debugging process that requires proof of root cause before allowing any code modifications.

소개

The Systematic Debug Workflow skill transforms how Claude handles bug reports by enforcing a disciplined, step-by-step methodology designed to eliminate trial-and-error. It guides the agent through mandatory phases—Triage, Reproduce, Hypothesize, Prove, and Fix—using 'adversary gates' that challenge logic and 'kickback logic' that reverts the process if predictions fail. By restricting tool access in early stages, it ensures a failing test is created and the root cause is verified before any production code is touched, leading to more stable and reliable software fixes.

주요 기능

Integrated CLI for tracking progress and workflow state
0 GitHub stars
Automated tool restrictions to prevent premature code editing
Mandatory reproduction step with test file enforcement
Adversary gates that challenge hypotheses and verify proof logic
Strict phase-based state management (Triage to Done)

사용 사례

Verifying root causes in mission-critical systems where side effects are risky
Investigating complex, intermittent bugs in large codebases
Ensuring regression tests are written before a fix is implemented

소개

주요 기능

Integrated CLI for tracking progress and workflow state
0 GitHub stars
Automated tool restrictions to prevent premature code editing
Mandatory reproduction step with test file enforcement
Adversary gates that challenge hypotheses and verify proof logic
Strict phase-based state management (Triage to Done)

사용 사례

Verifying root causes in mission-critical systems where side effects are risky
Investigating complex, intermittent bugs in large codebases
Ensuring regression tests are written before a fix is implemented