improve

Audits codebases and generates self-contained implementation plans for executor agents.

Updated Jul 17, 2026
One-click install
npx skills add https://github.com/usmangurowa/socialmocks --skill improve-usmangurowa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve
Source: https://github.com/usmangurowa/socialmocks/tree/main/.agents/skills/improve
Command: npx skills add https://github.com/usmangurowa/socialmocks --skill improve-usmangurowa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Codebase audits often produce vague advice that dies in a chat transcript, and handing improvement work to a fresh agent without context leads to broken or out-of-scope changes. This Skill surveys a repository as a read-only senior advisor, vets every finding against the actual code, and writes fully self-contained implementation plans that a separate executor model can carry out, verify, and be reviewed against. ## Core Features & Use Cases - Multi-category audit: Fans out read-only analysis across correctness, security, performance, test coverage, tech debt, dependencies, DX, docs, and product direction, with quick/standard/deep effort levels and parallel subagent support. - Self-contained handoff plans: Writes prioritized plan files under plans/ with inlined code excerpts, exact verification commands, scope boundaries, STOP conditions, drift checks, and a status index, so an executor with zero prior context can succeed. - Execution loop: Variants like execute <plan> dispatch an isolated-worktree executor subagent and review its diff like a tech lead, while reconcile keeps the plan backlog current and --issues publishes plans as GitHub issues. - Use Case: Point it at a TypeScript monorepo and ask for a security-focused audit; it maps the repo, verifies each finding against the source, presents a leverage-ranked table, and writes plans another agent can implement and test independently. ## Quick Start Ask the assistant to audit this repository with the improve skill and turn the top findings into executable plans.

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 and generate implementation plans for another AI agent?

Invoke the skill on the repository; it runs recon to map languages, frameworks, and verification commands, audits across nine categories, vets each finding against the actual code, then writes self-contained plan files under plans/ that an executor agent can follow without any prior context.

What does a code audit skill check for?

It covers correctness bugs, security issues, performance problems, test coverage gaps, tech debt and architecture, dependency and migration risks, developer experience and tooling, documentation, and product direction. Every finding requires file:line evidence, impact, effort, risk, and confidence ratings.

Can the skill modify my source code during an audit?

No. The advisor is strictly read-only on source code and may only create files under plans/ or advisor-plans/. Code changes happen only through a separate executor subagent working in an isolated git worktree, whose diff the advisor reviews without ever merging or committing.

How do I control the depth of a codebase audit?

Add quick or deep anywhere in the invocation; standard is the default. Quick covers hotspots with top high-confidence findings, deep audits the whole repo with up to eight parallel subagents, and a focus argument like security or perf limits the audit to one category.

What happens when the executor agent finishes a plan?

The advisor re-runs every done criterion in the worktree, checks the diff against the plan's in-scope file list, reads the new tests, and renders an APPROVE, REVISE, or BLOCK verdict. Merging remains the user's decision; the advisor never pushes or commits to the user's branch.

When should I not use an audit-and-plan workflow?

Skip it for trivial single-file fixes you can make directly, or when the repository lacks any working verification command and you first need a basic build or test baseline. The skill itself flags a missing verification baseline as the first finding in that situation.