Code Improver improves a skill, plugin, module or directory by looping a reviewer and a fixer subagent until a review reports zero critical or major findings. You name the reviewer, any installed skill or agent, and the glob scope the loop may touch.
The loop runs as a background Workflow with a cross-round ledger, an escalation when fixes stop converging, and a mechanical scope check after every fix round. It never commits, and it ends by stripping its own narration comments.
What You Get
- A loop that reviews, fixes and re-reviews up to a round cap, five by default
- A findings ledger on disk that carries over between runs
- Clear outcome labels, including capped and not converged when blocking issues remain
- Changes left in the working tree, never committed
Common Use Cases
- Iterating on a module until a chosen reviewer agent finds no blocking issues
- Hardening a plugin directory with a specific review skill
- Resuming a stopped loop after you decide how to handle an escalation
- Running review-and-fix in a scripted session by polling the task until it ends
What Makes It Unique
It has no default reviewer and no bundled one, so the loop is only as good as the reviewer you choose. Its guards sit in the workflow: it refuses to imitate the loop inline when Workflow is unavailable, halts if the reviewer is missing, and treats a capped run as a failure to report.
Under The Hood
The skill is an instruction file that checks paths with shell commands and launches a Workflow script from the same plugin. The workflow calls your chosen reviewer and a fixer subagent, which read and edit files inside the scope you gave, and it writes a ledger and metrics to disk. It uses git to check scope after each round and may initialize a repository if none exists, which it reports as a note. It does not fetch web pages or call outside APIs by itself, though your chosen reviewer might.