Skip to content

charlesjones-dev/ai-improve

v1.0.0MIT

Audits a codebase across nine categories and writes self-contained implementation plans that another agent or a cheaper model can carry out, each with exact files, steps that end in a check, scope limits and STOP conditions. It also writes a plan from a description or from another audit's report, hands a plan to an executor in a separate git worktree and reviews the result, and keeps the plans up to date as the code changes. It never changes source code itself

improve-audit

Audit a codebase as an advisor and write implementation plans for another agent or a cheaper model to carry out. Maps the repo and its build, test and lint commands, audits up to nine categories (bugs, security, performance, tests, tech debt, dependencies, tooling, docs and direction), re-reads every finding before it shows the table, and writes one self-contained plan to plans/ for each finding you pick. Never changes source code.

improve-execute

Hand one implementation plan from plans/ to a cheaper executor model in a separate git worktree, then review its work the way a tech lead reviews a pull request: run every done criterion again, check that the diff stays in the plan's scope, read the diff and the new tests, and give a verdict of approve, revise (two rounds at most) or block. Never edits code itself, and never merges, pushes or commits to your branch.

improve-plan

Write one self-contained implementation plan for another agent or a cheaper model to carry out, without a full audit. Takes a description of what to build or fix, or a findings report from another audit, or 'review' and an existing plan to check and tighten. Reads the repo for its conventions and its build, test and lint commands, then writes the plan to plans/ with exact files, steps that each end in a check, scope limits and STOP conditions. Never changes source code.

improve-reconcile

Bring the implementation plans in plans/ up to date with the code. Checks that finished plans still hold and that approved branches were merged, investigates blocked plans and rewrites them around the obstacle, refreshes plans whose files changed since they were written, and retires findings that were fixed some other way. Reports which plans are ready to run. Changes only the plans folder, never source code.