bugfixlisted

# /bugfix — Guided Bug-Fix Workflow Guard rail for the #1 bug-fix failure: **fixing before a failing test exists.** This skill walks [`workflow-bugfix.md`](../../rules/workflow-bugfix.md) (the single source of truth) and adds one hard, non-skippable gate — **Phase 3 must produce a test that fails on the current code before any fix is written.** > Why this exists: the rule alone was repeatedly skipped. This skill makes the > order explicit and the gate blocking. Read `workflow-bugfix.md` for the full > rationale; this file is the executable checklist. ## The non-negotiable sequence ``` Reproduce → Root-Cause Analysis → FAILING TEST → Fix → Verify → Review → Commit ``` Each phase finishes before the next starts. The **only** way past Phase 3 is a test that you have **run** and **watched fail** for the right reason. ## Phase 1 — Reproduce (no guessing) - State the exact wrong behavior: command, input, observed vs expected. - Find the surface: which entry point(s)? CLI command, TUI path, library seam? A bug often lives on more than one surface (e.g. a CLI path AND its TUI twin); list every one that shares the broken code. - Confirm it actually reproduces. If you can't reproduce it, keep digging — **no speculative fixes.** Write a one-line repro: `"<cmd/inputs> → <observed>; expected <expected>"`. ## Phase 2 — Root-Cause Analysis (write it down) - Trace the symptom to the line **and** the condition that made it fire. - Output a root-cause statement in this exact sh