How do I install the Analyze Codebase For Improvements skill?

Run npx skillmds@latest add dalehurley/analyze-codebase-for-improvements in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Analyze Codebase For Improvements safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Analyze Codebase For Improvements?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Analyze Codebase For Improvements free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Analyze Codebase For Improvements?

dalehurley (@dalehurley) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Analyze Codebase For Improvements by dalehurley

Name: Analyze Codebase For Improvements
Author: dalehurley

Analyze Codebase For Improvements

Analyze a codebase or project to identify actionable improvements, architectural enhancements, and optimization opportunities. Use this skill when the user asks to review code quality, suggest improvements, identify bottlenecks, audit a system, or get recommendations for enhancing a project. Generates a prioritized list of improvements with problem statements, solutions, and impact analysis.

dalehurley 016a668 2.6 KB Updated Sep 17, 2026

File contents

Analyze Codebase for Improvements

Input Parameters

Parameter	Required	Description	Example
`project_path`	Yes	Path to the root directory of the project or codebase to analyze	~/Code/GitHub/phpbot
`focus_areas`	No	Comma-separated list of specific areas to prioritize	performance, error-handling, documentation
`project_type`	No	Type of project for context-aware recommendations	PHP application

Procedure

Confirm the project path, scope, and priority areas with the user if not provided

Examine directory layout, file counts, and key components:

ls -la {{PROJECT_PATH}}
find {{PROJECT_PATH}}/src -name "*.{{EXTENSION}}" | wc -l
grep -r "TODO\|FIXME\|HACK" {{PROJECT_PATH}}/src 2>/dev/null | head -20

Review README, configuration files, and recent changes to identify architectural pain points
Generate 8–12 actionable improvements organized by impact and effort — each with a problem statement, proposed solution, and expected benefit
Rank by value-to-effort ratio; surface quick wins first, then strategic long-term enhancements
Deliver as structured markdown with code examples and implementation steps where relevant

Notes

Each improvement must have a clear problem statement to justify the recommendation
Consider the project's current maturity level and team capacity when scoping changes

Example

what are 10 things I could do to improve this codebase
audit this project and suggest architectural improvements
identify technical debt and quick wins in this repo
review code quality and suggest optimizations
what are the biggest bottlenecks in this codebase

---name: analyze-codebase-for-improvementsdescription: Analyze a codebase or project to identify actionable improvements, architectural enhancements, and optimization opportunities. Use this skill when the user asks to review code quality, suggest improvements, identify bottlenecks, audit a system, or get recommendations for enhancing a project. Generates a prioritized list of improvements with problem statements, solutions, and impact analysis.---# Analyze Codebase for Improvements## Input Parameters| Parameter | Required | Description | Example || -------------- | -------- | --------------------------------------------------------------------------------------------------------- | ------------------------------------------ || `project_path` | Yes | Path to the root directory of the project or codebase to analyze | ~/Code/GitHub/phpbot || `focus_areas` | No | Comma-separated list of specific areas to prioritize | performance, error-handling, documentation || `project_type` | No | Type of project for context-aware recommendations | PHP application |## Procedure1. Confirm the project path, scope, and priority areas with the user if not provided2. Examine directory layout, file counts, and key components: ```bash ls -la {{PROJECT_PATH}} find {{PROJECT_PATH}}/src -name "*.{{EXTENSION}}" | wc -l grep -r "TODO\|FIXME\|HACK" {{PROJECT_PATH}}/src 2>/dev/null | head -20 ```3. Review README, configuration files, and recent changes to identify architectural pain points4. Generate 8–12 actionable improvements organized by impact and effort — each with a problem statement, proposed solution, and expected benefit5. Rank by value-to-effort ratio; surface quick wins first, then strategic long-term enhancements6. Deliver as structured markdown with code examples and implementation steps where relevant## Notes- Each improvement must have a clear problem statement to justify the recommendation- Consider the project's current maturity level and team capacity when scoping changes## Example```what are 10 things I could do to improve this codebaseaudit this project and suggest architectural improvementsidentify technical debt and quick wins in this reporeview code quality and suggest optimizationswhat are the biggest bottlenecks in this codebase```

Frequently asked questions