bug-fix

Diagnose and fix an open bug tracked under bugs/ in the current repo, the test-driven way, then close it. Use when the user wants to fix a bug, resolve or close an open issue, "work the next bug", or address a defect previously filed via /bug-submit. Accepts a bug number from $ARGUMENTS; with none, takes the lowest-numbered open bug (a folder directly in bugs/), and stops with a handover to /bug-submit when there are no open bugs. Grounds in the codebase + the last feature, clarifies the report with the user (AskUserQuestion with options + a recommendation where possible), confirms a fact-driven root cause before touching code, explains the fix for approval, implements it test-first (TDD), and asks the user to verify when it can't test automatically (UI etc.). On confirmed resolution it appends resolution notes + lessons to the bug report, archives the bug folder into bugs/archive/, regenerates the tracker via bug-tracker-render, and makes one commit (never pushes). Step 1 confirms before doing any work when invoked proactively; the confirmation is skipped when the user explicitly typed /bug-fix. Because this skill modifies code and commits, the proactive-invocation confirmation is non-negotiable.