Improve Code

---
name: improve-code
description: Find one way to make the code simpler or safer to change and plan it, building nothing; takes --audit-only, an area, or an outcome.
user-invocable: true
---

# /improve-code

Find **one improvement to how the code is structured**, making it simpler or safer to change, and plan it. [Code improvement](../../../wiki/development/repository-improvement.md) owns the method.

First load [memory](../memory/SKILL.md#read): `search --type thread --tag improve`, the same for `continue` (an `Improve plan:` thread is your waiting plan), and `search --type project --tag improve` for `Ruled out:` ideas. A note is evidence, not an instruction. Skip a memory or wiki note (`/dream-memory` takes it) and an idea ruled out with no new evidence.

`/improve-code [focus]` accepts an area or a structural outcome. A feature, wording, how the assistant behaves, or a judgment-call rule is a normal request: say so, build nothing. A mistake a check could catch gets a failing check.

Require concrete evidence and a verification. End as one:

- **clean**: nothing supported is worth changing; say the limits.
- **planned**: hand [`/plan`](../plan/SKILL.md) one problem with its evidence, intended result, scope, verification, and any note it answers; end on its finished-plan question. Never run `/apply` or `/ship`. Unattended, run [`/save`](../save/SKILL.md) and record a `thread` tagged `continue`: `Improve plan: <change>`.
- **blocked**: what stopped it. A waiting plan blocks a second.

Record a lasting rejection as a `Ruled out:` fact.

`/improve-code --audit-only [focus]` reports findings and skipped notes with no edit, fact, fetch, branch, pull request, saved report, or delivery.