improve
From the author
Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.
Install
npx skills add gadicc/yahoo-finance2 --skill improve -a claude-code
Installs to .claude/skills/improve/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 87
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- improve-architecturerohitg00/pro-workflowAudit an area of the codebase and propose the smallest structural moves that improve it - untangle boundaries, kill duplication, fix seams, break cycles. Produces a prioritized plan and decision records, not a rewrite. Use when a codebase feels tangled, hard to change, or is becoming a ball of mud, or when asked to improve or refactor architecture.Planning★ 2.9K
- code-review-assistantArabelaTso/Skills-4-SEConduct comprehensive code reviews identifying bugs, security issues, performance problems, code quality concerns, and best practice violations. Use when reviewing pull requests, examining code changes, evaluating new code, assessing code quality, or providing feedback on implementations. Analyzes code for correctness, security vulnerabilities, performance bottlenecks, maintainability issues, test coverage, documentation quality, and adherence to coding standards. Produces structured markdown reviews with categorized findings, severity ratings, specific examples, and actionable recommendations. Triggers when users ask to review code, check pull requests, evaluate implementations, find bugs, or assess code quality.Engineering★ 259
- improve-codebase-architecturemxyhi/ok-skillsScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.Planning★ 506
- deep-module-refactorzebbern/claude-code-guideExplore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.Engineering★ 4.7K
- code-reviewphuryn/pm-skillsReview code for actionable defects. Correctness is the core; performance and security are optional sub-cases of the same engine. Anchors on agreements between participants across a boundary, forces a violating execution, and refutes every candidate before reporting. Use when asked to review changes, find bugs, audit a codebase, or check whether a fix is safe.Engineering★ 27.4K
- design-architectureSenolIsci/mykgReviews the current codebase architecture and proposes improvements using four parallel specialist subagents: System Architect, Software Architect, Data Architect, and an Adversarial Architect that red-teams failure paths, LLM adversarial output scenarios, silent corruption risks, and invariant bypasses. Each subagent independently analyzes the codebase from their domain perspective, then their findings are consolidated into a living `architecture.md` file with a tracked to-do list and change log. Use this skill whenever the user asks to review, analyze, audit, or improve the architecture — or when they ask questions like "what should we change structurally?", "how is the system organized?", "what are our architecture problems?", "can you do an architecture review?", or "let's redesign X". Also trigger when the user mentions technical debt, structural improvements, security concerns, failure modes, vulnerabilities, or wants a second opinion on design decisions, even if they don't use the word "architecture".Design★ 79
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in