improve is an agent skill that audits codebases and writes implementation plans for other agents to execute.
The tool solves the problem of inefficient use of capable models by separating the intelligence-intensive work of understanding a codebase and deciding what matters from the execution work of implementing changes. It uses a capable model to map the repository, audit it across nine categories (correctness, security, performance, test coverage, tech debt, dependencies, developer experience, documentation, and feature direction), and write detailed plans. Those plans are then handed to cheaper models or humans for execution. The approach works by first performing reconnaissance to understand the repository's stack, conventions, build and test commands, and any existing design documentation. It then fans out parallel audits across the nine categories, with each finding carrying file-line evidence, impact, effort, and confidence scores. Before presenting findings, the tool re-verifies each cited location to filter false positives. The user selects which findings to plan, and the tool generates one markdown file per plan with exact steps, verification gates using the repository's own test and lint commands, and stop conditions for when reality diverges from expectations.
The tool suits teams that want to systematize code improvement without burning expensive model tokens on execution. It works well for repositories that maintain design documentation like architecture decision records, product requirements, or context files, since it ingests these to avoid re-flagging decided tradeoffs. The plans are plain markdown, so they can be executed by any agent or reviewed by humans before implementation. The skill integrates with any agent supporting the Agent Skills format.
The project maintains a workflow that supports iterative improvement: users can run a quick audit, select findings to plan, execute plans in isolated worktrees with diff review, and then reconcile the backlog in subsequent sessions to verify what landed and refresh what drifted. A branch-scoped mode lets teams audit only the changes in a pull request before submission.
