vibe-fix-buglisted

Full spec-driven workflow for diagnosing and fixing a bug with an AI coding agent. Triggers on "bug:" prefix, "I have a bug", "something is broken", "this is not working", "fix this issue", "there is a bug in", "debug this", "broken", "issue". Always use when the user reports unexpected behaviour — even without the exact prefix. Three-way severity triage: trivial bugs (3 tasks, no folder), environment bugs (runs vibe-doctor first, no BUG_SPEC), significant bugs (full workflow). Environment bugs — HMR loops, missing deps, config mismatches, build tool failures — are detected at triage and routed to vibe-doctor rather than full bug workflow. Diagnosis always before the fix. Regression test always before fix code. BUG_SPEC.md, BUG_PLAN.md, BUG_TASKS.md created for significant bugs only.
aakashdhar/vibe-skill · ★ 7 · AI & Automation · score 68

Install: claude install-skill aakashdhar/vibe-skill

# Vibe Fix Bug Skill Spec-driven bug diagnosis and surgical fixing. Diagnosis before fix. Regression test before fix code. Smallest possible change. **Use Plan Mode (Shift+Tab) for Steps 1–5. Exit before Step 6.** --- ## The O'Reilly principles this enforces **Spec before code** — root cause confirmed and fix plan approved before any code changes. **Context preservation** — CODEBASE.md read first, ARCHITECTURE.md patterns followed. **Incremental verifiable progress** — regression test first, fix second, verify third. **Drift prevention** — DECISIONS.md updated, ARCHITECTURE.md updated if fix reveals new pattern. --- ## Two audiences. Two file types. **Human-facing:** - `vibe/TASKS.md` — plain English, updated after every task **Agent-facing (human never opens these):** - `vibe/bugs/[date-slug]/BUG_SPEC.md` · `BUG_PLAN.md` · `BUG_TASKS.md` - `vibe/CODEBASE.md` · `vibe/ARCHITECTURE.md` · `vibe/DECISIONS.md` --- ## Step 1 — Gather the bug report and triage severity Extract or ask for: - **What's happening** — the symptom - **What should happen** — expected behaviour - **Steps to reproduce** — how to trigger it - **Frequency** — always / sometimes / only under X - **Errors or logs** — any messages or stack traces **Triage — three paths:** **Environment bug** — route to vibe-doctor, NOT the bug workflow: Check for these signals first: - App won't start / server fails to launch - WebSocket/HMR connection errors - `Cannot find module`, `MODULE_NOT_FOUND` - Tailwind cl