FradSer 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:
- Run
git rev-parse --is-inside-work-tree; if false, inform user that project-wide mode requires a git workspace - Record current revision with
git rev-parse --short HEADand include it in final summary for rollback context - Ignore command arguments and proceed with full-project discovery
Phase 1: Analyze Project Scope
Goal: Discover all code files and display scope summary.
Actions:
- Find all code files using Glob patterns for common extensions
- Filter out
node_modules/,.git/,dist/,build/,vendor/,.venv/ - Group files by language/extension and identify primary source directories
- 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:
- Launch
refactor:code-simplifieragent with all discovered code files - Pass cross-file optimization emphasis: duplication reduction, consistent patterns
- Pass aggressive mode flag for legacy code removal
- Agent auto-loads
refactor:best-practicesskill 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:
- Report total files refactored (count and percentage of project)
- List changes categorized by improvement type and cross-file improvements made
- List best practices applied and legacy code removed
- Suggest test suite to run and recommend reviewing changes in logical groups
- 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