refactor-project
Executes automated project-wide refactoring with a focus on cross-file optimization. This skill should be used when the user asks for project-wide refactoring, cross-file simplification, consistency standardization across the codebase, duplication reduction, or invokes "/refactor-project".
Best use case
refactor-project is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Executes automated project-wide refactoring with a focus on cross-file optimization. This skill should be used when the user asks for project-wide refactoring, cross-file simplification, consistency standardization across the codebase, duplication reduction, or invokes "/refactor-project".
Teams using refactor-project should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/refactor-project/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How refactor-project Compares
| Feature / Agent | refactor-project | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Executes automated project-wide refactoring with a focus on cross-file optimization. This skill should be used when the user asks for project-wide refactoring, cross-file simplification, consistency standardization across the codebase, duplication reduction, or invokes "/refactor-project".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# Refactor Project Command Execute automated project-wide refactoring using `refactor:code-simplifier` agent with cross-file optimization focus. ## Pre-operation Checks **Goal**: Ensure project-wide execution is explicit and reproducible. **Actions**: 1. Run `git rev-parse --is-inside-work-tree`; if false, inform user that project-wide mode requires a git workspace 2. Record current revision with `git rev-parse --short HEAD` and include it in final summary for rollback context 3. Ignore command arguments and proceed with full-project discovery ## Phase 1: Analyze Project Scope **Goal**: Discover all code files and display scope summary. **Actions**: 1. Find all code files using Glob patterns for common extensions 2. Filter out `node_modules/`, `.git/`, `dist/`, `build/`, `vendor/`, `.venv/` 3. Group files by language/extension and identify primary source directories 4. Display scope summary (file count, languages, directories) then proceed automatically See `references/scope-analysis.md` for exclusion patterns and edge cases. ## Phase 2: Launch Refactoring Agent **Goal**: Execute `refactor:code-simplifier` agent with project-wide scope and cross-file focus. **Actions**: 1. Launch `refactor:code-simplifier` agent with all discovered code files 2. Pass cross-file optimization emphasis: duplication reduction, consistent patterns 3. Pass aggressive mode flag for legacy code removal 4. Agent auto-loads `refactor:best-practices` skill and applies language-specific patterns See `references/agent-configuration.md` for detailed Task parameters. ## Phase 3: Summary **Goal**: Report comprehensive summary of project-wide changes. **Actions**: 1. Report total files refactored (count and percentage of project) 2. List changes categorized by improvement type and cross-file improvements made 3. List best practices applied and legacy code removed 4. Suggest test suite to run and recommend reviewing changes in logical groups 5. Provide safer rollback command tied to recorded baseline (for example: `git restore --worktree --staged .`) See `references/output-requirements.md` for detailed summary format. ## Requirements - Execute immediately after displaying scope (no confirmation needed) - Refactor entire project across all discovered code files - Prioritize cross-file duplication reduction and consistent patterns - Preserve behavior and public interfaces unless user explicitly requests a behavior change
Related Skills
refactor
Executes automated refactoring for specific files, directories, or semantic queries. This skill should be used when the user asks to refactor specific files or directories, simplify recently changed code, clean up dead code in a limited scope, or invokes "/refactor".
update-readme
Updates README.md and README.zh-CN.md to reflect the project's current state. Use this skill whenever the user asks to "update the README", "sync the docs", "update documentation", "reflect latest changes in README", or wants both the English and Chinese READMEs to match the current project. Always triggers when the user mentions updating or regenerating README files, especially for bilingual (EN/ZH) projects.
swiftui-review
Reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. This skill should be used when the user asks to review SwiftUI code, check for deprecated iOS/macOS APIs, validate data flow patterns, or audit accessibility compliance in Swift projects.
writing-plans
Creates executable implementation plans that break down designs into detailed tasks. This skill should be used when the user has completed a brainstorming design and asks to "write an implementation plan" or "create step-by-step tasks" for execution.
systematic-debugging
Provides a systematic debugging methodology with a 4-phase root cause analysis process. This skill should be used when the user reports a bug, error, test failure, or unexpected behavior, ensuring thorough investigation precedes any code changes.
need-vet
This skill should be used when the user invokes /need-vet to enable work verification for the current task. Claude must verify completion and append the verified tag before the session can end.
executing-plans
Executes written implementation plans efficiently using agent teams or subagents. This skill should be used when the user has a completed plan.md, asks to "execute the plan", or is ready to run batches of independent tasks in parallel following BDD principles.
build-like-iphone-team
Applies Apple's Project Purple design philosophy for radical innovation. This skill should be used when the user wants to challenge industry conventions, approach open-ended problems requiring disruptive thinking, or when standard brainstorming needs a breakthrough approach.
brainstorming
Structures collaborative dialogue to turn rough ideas into implementation-ready designs. This skill should be used when the user has a new idea, feature request, ambiguous requirement, or asks to "brainstorm a solution" before implementation begins.
behavior-driven-development
Applies behavior-driven development principles including Gherkin scenarios and test-driven development. This skill should be used when the user asks to implement features, fix bugs, or when writing executable specifications and tests before writing production code.
agent-team-driven-development
Provides guidance on coordinating multiple specialized teammates working in parallel. This skill should be used when the user needs to execute complex implementation plans, resolve cross-cutting concerns, or coordinate independent work streams requiring communication.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".