improve

Audits codebases read-only and produces evidence-backed improvement suggestions with routing decisions.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/leonardoacosta/skills --skill improve-leonardoacosta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve
Source: https://github.com/leonardoacosta/skills/tree/main/leo-core/skills/improve
Command: npx skills add https://github.com/leonardoacosta/skills --skill improve-leonardoacosta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Engineering teams often lack a structured way to identify what to fix or build next in a codebase. This Skill performs a read-only audit of a repository, gathers file:line evidence, vets findings by impact and effort, and routes each selected suggestion into the repository's canonical OpenSpec and Beads workflow without inventing parallel backlogs. ## Core Features & Use Cases - Read-only codebase audits: Covers correctness, security, performance, tests, architecture, dependencies, developer experience, and documentation at quick, standard, or deep effort levels. - Scoped reviews: Supports domain audits (security, performance, tests), branch reviews labeling findings as introduced or pre-existing, roadmap direction analysis, and plan or proposal reviews. - Self-contained suggestion contracts: Every selected finding includes evidence, definition of done, blast radius, and exactly one route (attach, feature, ad-hoc task, or research/decision map) so a fresh executor can act without session context. - Use Case: Ask for a security audit of your repository before a release; the advisor inspects input boundaries, secret handling, and authz checks, then returns a prioritized list of verified findings with an ordered execution queue. ## Quick Start Ask the agent to audit this repository and tell you what to improve next, optionally scoping it to a domain like security or a branch review.

Frequently Asked Questions about improve

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a codebase for improvements with an AI agent?

Invoke the improve skill with an optional effort level (quick, standard, or deep) and scope such as a domain, branch, or roadmap. It reads repository guidance, audits code with file:line evidence, and returns vetted findings with an ordered execution queue.

How to review whether an existing plan or proposal is executable?

Use the review-plan scope with a proposal ID or slug. The advisor checks evidence, ambiguity, scope boundaries, verification coverage, and completion gaps, then returns a ready, revise, or blocked verdict without modifying the implementation.

Does the improve skill modify code or create tasks automatically?

No. The audit is strictly read-only: it never edits source, commits, or creates work items unless the user explicitly authorizes capture or execution. Selected findings are routed to the repository's canonical OpenSpec and Beads workflow.

Can it review only the changes on my current branch?

Yes. The branch scope inspects changes since the default-branch merge base plus direct callers and importers, labeling each finding as introduced or pre-existing so reviewers can separate new issues from legacy debt.

What happens when a finding is too uncertain to implement?

Findings that lack enough certainty for an honest implementation contract are routed as research or decision-map items. Decisions and dependencies are preserved in the existing hierarchy instead of creating speculative execution tasks.