fixlisted

# /gku:fix — find what is wrong, then fix it Two jobs in one command, because in practice they are the same job. **Given findings** — from a `/gku:review` in this conversation, or a review report file — it applies them: smallest change first, one commit per finding, then re-runs the tests. That is the half `/gku:review` deliberately leaves undone. **Given a symptom** — a sentence describing something that is broken — it investigates first. Classify the request, find the code, prove the cause, *then* fix it. This is the same investigation `/gku:plan` performs, with one difference that matters: when the cause is proven and the fix is clear, **it acts** rather than handing you a plan file to run separately. That makes it the natural way to open a fresh session on a bug report. Nothing needs to be in the conversation already. It writes code. It **does not push and does not open a pull request** — that is `/gku:pr`. **It never fixes blindly.** A finding is a claim about code, and a sentence is a claim about behaviour. Neither is a licence to edit. Findings are re-checked against what is actually there, and symptoms are traced to a cause you can quote, before anything changes. ## Arguments - **nothing** — fix the findings from a `/gku:review` earlier in this conversation. If there are none, run the review analysis inline first (step 2) and fix what it finds. - **A sentence** — `/gku:fix the export blows up when a department has no head`. A symptom, not a location: it ge