Agent skill · trailofbits
code-improver
Runs an autonomous review-and-fix improvement loop over any code target — a skill, plugin, module, or directory — using a reviewer the user names: any installed skill or agent. Keeps a cross-round findings ledger, escalates when fixes stop converging, and guards scope mechanically. Use when asked to 'improve this code until review passes', 'run an improvement loop with <reviewer>', or to iterate review-and-fix with a specific reviewer. For skills prefer the skill-improver entry; for a branch prefer pr-improver.
What it needs
About 4k tokens when loaded.
What this skill does
Code Improver Improve any code target by running /code-improver:improve — a dynamic workflow that loops the named reviewer and a fixer subagent until a review reports zero critical/major findings, then strips its own residue. The loop, its ledger, and its guards live in the workflow; this skill collects the three inputs the generic entry requires and relays the outcome. Starting the loop The user provided: $ARGUMENTS (if empty, take the details from the conversation). 1. Collect the three required inputs — no guessing 1. Target: the absolute path to the directory under improvement. Resolve relative paths against the working directory; verify the directory exists. 2. Reviewer: the installed skill or agent that performs every review. The user must name it — there is no default and no bundled reviewer. Determine the kind: a namespaced agent (e.g. plugin-dev:skill-reviewer) → "kind": "agent" an installed skill (e.g. pr-review-toolkit:review-pr) → "kind": "skill" If the name could be either, check the session's skill listing; if still ambiguous, ask the user. If no reviewer was named, ask — do not pick one. 3. Scope: repo-relative globs the loop may touch. The generic entry requires it explicitly; if the user did not give one, propose the target directory (<repo-relative-target>/) and confirm before launching. 2. Resolve the loop script The loop is the dynamic workflow workflows/improve.js in this plugin. Launch it by path: scriptPath takes a resolved absolute path, and the Workflow tool's name resolves built-in and project workflows, so a marketplace-installed one may not answer to code-improver:improve. Try in order, first hit wins — the home directories come before . so an installed copy beats a checkout of this marketplace: 1. Bash: ls -d -- "${CLAUDEPLUGINROOT}/workflows/improve.js" 2. Bash: ls -d -- "${CODEXPLUGINROOT}/workflows/improve.js" (if that variable is set instead) 3. Bash: find ~/.claude ~/.codex . …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills trailofbits/code-improver