spectra-debug
FeaturedSystematically debug a problem using a four-phase workflow
Testing & QA 45 stars
3 forks Updated today MIT
Install
Quality Score: 90/100
Stars 20%
Recency 20%
Frontmatter 20%
Documentation 15%
Issue Health 10%
License 10%
Description 5%
Skill Content
Systematically debug a problem using a four-phase workflow.
**This skill enforces debugging discipline.** No guessing, no random changes, no "let me try this." Every step is deliberate and evidence-based.
**Input**: The argument after `/spectra:debug` describes the bug or unexpected behavior. Examples:
- `/spectra:debug the search returns duplicate results`
- `/spectra:debug crash on startup after upgrading`
- `/spectra:debug file watcher misses rename events`
---
## The Three-Attempt Rule
**Maximum 3 fix attempts per hypothesis in Phase 4 (Fix).** Phases 1-3 (Reproduce, Isolate, Root Cause) are investigation — they do not count toward this limit. If your third fix attempt fails:
1. **Stop fixing**
2. Document what you tried and why it failed
3. Question your hypothesis — is the root cause what you think it is?
4. Research alternatives or try a completely different angle
Do NOT keep trying variations of the same approach. That's a loop, not debugging.
---
## Phase 1: Reproduce
Before anything else, make the bug happen reliably.
- **Find the exact steps** to trigger the bug
- **Identify the expected vs actual behavior** — be precise
- **Determine if it's consistent** — does it happen every time? Only on certain input?
- **Simplify the reproduction** — strip away everything that's not essential
If you can't reproduce it, you can't debug it. Gather more information before proceeding.
---
## Phase 2: Isolate
Narrow down where the bug lives.
- **Binary search the ...
Details
- Author
- YuDefine
- Repository
- YuDefine/nuxt-supabase-starter
- Created
- 7 months ago
- Last Updated
- today
- Language
- JavaScript
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category