08-debug
/08-debug
Reproduce and fix a known bug, or find an unknown root cause by hypothesis validation. Use when the user wants to fix a bug, find why something breaks, or reopen a stuck investigation. Not for building a feature or reviewing a diff.
- Author
- ai-driven-dev ↗
- Repository
- framework ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 6
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Reproduce and fix a known bug, or find an unknown root cause by hypothesis validation. Use when the user wants to fix a bug, find why something breaks, or reopen a stuck investigation. Not for building a feature or reviewing a diff.
Arguments
/08-debug bug | symptom
Original author description
Reproduce and fix a known bug, or find an unknown root cause by hypothesis validation. Use when the user wants to fix a bug, find why something breaks, or reopen a stuck investigation. Not for building a feature or reviewing a diff.
How it works
- Actions
- Transversal rules
- Assets
- References
SKILL.md preview
--- name: 08-debug description: Reproduce and fix a known bug, or find an unknown root cause by hypothesis validation. Use when the user wants to fix a bug, find why something breaks, or reopen a stuck investigation. Not for building a feature or reviewing a diff. argument-hint: bug | symptom --- # Skill: debug Diagnose and fix issues through structured hypothesis validation, root-cause analysis, and a test-driven fix. ## Actions | # | 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: reopen the search space, instrument logs first | Pick the one action matching the intent; never default to `01`. Triggers like "reproduce and fix" route to `01`, "why does this happen" to `02`, "I'm stuck" or "previous fixes didn't work" to `03`. Ask one question when the intent is ambiguous. Before running an action, read its file in `actions/`, not only the table or assets. ## Transversal rules - One action per run: follow only the matching action file. - Scope each fix to its bug: never bundle drive-by refactors. - Confirm the root cause before fixing; the diagnostic actions stop at a confirmed cause. ## Assets - `assets/task-template.md`: the per-hypothesis tracking file the debug action fills. ## References - `references/mermaid-conventions.md`: the project's Mermaid conventions for the action-path flowchart.
Files in this package (6)
- SKILL.md 2 KB
- actions/01-reproduce.md 1 KB
- actions/02-debug.md 2 KB
- actions/03-reflect-issue.md 1 KB
- assets/task-template.md 1 KB
- references/mermaid-conventions.md 1 KB
Versions
The database has no other skills named 08-debug.
Database snapshot: 13.11.2026 · package version dda5d4722a53 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 96fix-bug
Fix a defect: reproduce it, write a failing test, find the root cause, fix it and record the lesson. Use for each bug. - 100bug-fix
Fix a Device bug the project's way - reproduce it, write a small failing test, find the root cause, fix it, prove the test now passes. Use for any bug report or broken feature; escalates to a spec when the cause or fix is not obvious. - 90fix-issue
Use when fixing a GitHub issue — reproduce, trace root cause, fix, add regression test - 100fix-bug
Reproduce the bug, find the root cause, fix it there, and verify against the repro with prove-it-works. Use for any defect report; not for a direct fix in Normal mode when no repro-first loop is needed, and not for a performance regression (use tune-perf). - 100fix
Use when fixing a bug test-first: write a failing test to reproduce it, find the root cause, fix, and add a regression test. - 100debug-systematically
Use when a bug resists the first fix — reproduce it, bisect to the introducing change, test one hypothesis at a time, fix the root cause, and add a regression test.