code improver

Engineering Community

Skill notes

Starting the loop

The user provided: $ARGUMENTS (if empty, take the details from the conversation).

1. Collect the three required inputs — no guessing

Target: the absolute path to the directory under improvement. Resolve relative paths against the working directory; verify the directory exists. 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"

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:

3. Invoke the workflow

Run it with the Workflow tool, {scriptPath: "<the path from step 2>", args: {...}}: maxRounds only if the user asked for a different cap. pluginRoot lets the run find its metrics collector; omit the key only if step 2 fell through to the workflow name — the workflow then searches for itself. finalize ({"version_bump": bool, "narration_strip": bool, "docs_pass": bool}) only

Relaying the result

The workflow returns a structured result. Report it honestly — the distinctions matter: converged: true — the last action was a review with zero critical/major findings. Report rounds used, remaining minor findings (open_minor_count), and the artifact paths (ledger_path, metrics). capped: true — the fix budget ran out and the FINAL review still found blocking

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@trailofbits · no license declared
Token usage
Moderate
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview code-improver.preview
# Relaying the result

- **`converged: true`** — the last action was a review with zero critical/major findings.
- **`capped: true`** — the fix budget ran out and the FINAL review still found blocking
- **`escalation`** — the loop detected it was not converging (recurring findings,
- **`halted`** — a guard fired (scope violation, unregistered new files, a dead or
- **`notes`** always travel with the result — surface them; they include loud warnings

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.