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".

```

Provide a comprehensive summary after refactoring completes. Use this exact structure:

When arguments contain both valid paths and semantic descriptions:

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".

```

Provide a comprehensive summary after project-wide refactoring completes. Use this structure:

Use language-specific patterns to discover all code files:

Use this agent when the user asks to refactor code, simplify complex logic, remove dead or legacy code, apply framework-specific performance patterns, or run `/refactor` and `/refactor-project` workflows while preserving behavior. <example> Context: User wants to refactor specific files for clarity user: "/refactor src/auth/login.ts" assistant: "I'll launch the code-simplifier agent to refactor the specified file, load the refactor:best-practices skill with relevant references, apply minimal behavior-preserving improvements, and summarize changes." <commentary> The request is scoped to specific file paths and fits a behavior-preserving refactor workflow. </commentary> </example> <example> Context: User wants to clean up unused code and simplify logic user: "Clean up unused code and simplify the complex logic in this module" assistant: "I'll launch the code-simplifier agent to identify dead code, remove unused imports/exports/variables, simplify complex patterns while preserving behavior, and provide a summary of improvements." <commentary> Request combines dead code removal with logic simplification, requires aggressive cleanup mode. </commentary> </example> <example> Context: User wants to apply framework-specific performance optimizations user: "Apply Next.js performance best practices to this component" assistant: "I'll launch the code-simplifier agent to detect the Next.js framework, load relevant performance references from refactor:best-practices, apply only applicable optimizations (waterfalls, bundle impact, hydration), and summarize changes." <commentary> Framework-specific request requires detection and selective application of Next.js rules. </commentary> </example> <example> Context: User wants project-wide refactoring for consistency user: "/refactor-project" assistant: "I'll launch the code-simplifier agent with project-wide scope to scan the entire codebase, prioritize cross-file duplication reduction and pattern standardization, and summarize changes with suggested tests." <commentary> Project-wide scope requires consistent cross-file application and duplication detection. </commentary> </example>

Language-specific best practices, code quality standards, and framework detection rules. Use when executing refactoring workflows, applying code quality rules, detecting frameworks, or checking language-specific patterns for TypeScript, Python, Go, Swift, or React.

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".

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".