debug
Debug
When something breaks, stop building. Preserve evidence, diagnose the root cause, fix it, guard against recurrence. Guessing wastes time.
Workflow
1. Stop the line
Stop adding features or making changes. Errors compound — a bug in step 3 makes steps 4-10 wrong.
2. Reproduce
Make the failure happen reliably. Run the specific failing test in isolation. If you can't reproduce it, you can't fix it with confidence.
3. Localize
Narrow down where the failure occurs:
- Which layer is failing?
- Which change introduced it? (use
git bisectfor regressions)
More from cniska/skills
tdd
Drive implementation with red-green-refactor. Use when building features or fixing bugs test-first.
12review
Run all review skills against the current branch diff. Use when reviewing a feature branch before merge.
10plan
Design a feature or behavior change through dialogue. Use when asked to plan, scope, design, or break down work before coding.
10explore
Explore a task or design through systematic questions until reaching shared understanding. Use before implementing complex or ambiguous work.
10issue
Create a GitHub issue from a short description. Use when filing a bug, feature request, or task.
10pr
Create a pull request with review and verify. Use when the branch is ready to merge.
10