Stats
Actions
Tags
From aidd-dev
Systematically reproduces and fixes bugs using test-driven workflow, root cause analysis, and hypothesis validation. Supports fix-to-PR, unknown root cause debugging, and stuck/reflection modes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/aidd-dev:08-debugopusThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Diagnoses issues through structured hypothesis validation, root cause analysis, and test-driven bug fixing from issue creation to PR.
Diagnoses issues through structured hypothesis validation, root cause analysis, and test-driven bug fixing from issue creation to PR.
| # | Action | When to use |
|---|---|---|
| 01 | reproduce | A known bug must be fixed end to end: reproduce, test-driven fix, branch, PR |
| 02 | debug | Root cause unknown: enumerate hypotheses, validate each, confirm the cause |
| 03 | reflect-issue | Stuck or prior fixes failed: re-open the search space, instrument logs first |
This skill offers three distinct actions. Pick the ONE matching the user's intent; do NOT default to action 01.
01-reproduce02-debug03-reflect-issueIf the intent is ambiguous, ask one clarifying question before picking. Then read and follow only the matching action file.
@actions/01-reproduce.md@actions/02-debug.md@actions/03-reflect-issue.mdnpx claudepluginhub ai-driven-dev/frameworkApplies Zeller's scientific method to debug software: reproduce, hypothesize, binary-search isolate, fix root cause, add regression test. Triggers on bug, error, crash, stack trace.
Enforces systematic root cause investigation for bugs, test failures, and unexpected behavior through four phases: investigation, pattern analysis, hypothesis testing, and implementation.
Forces a scientific-method loop (Observe → Hypothesize → Experiment → Conclude) to debug non-trivial bugs. Prevents guessing by ensuring evidence before fixes.