| name | refactor |
| description | Refactor code to improve quality without changing behavior |
| argument-hint | [file or function] |
| disable-model-invocation | true |
Refactor the code at $ARGUMENTS to improve its quality.
Principles
- Preserve behavior - Tests should pass before and after
- Small steps - Make incremental changes
- One thing at a time - Don't mix refactoring with new features
Common Refactorings
Extract
- Extract function: Pull out a block into a named function
- Extract variable: Name a complex expression
- Extract constant: Replace magic numbers/strings
Simplify
- Remove dead code: Delete unused functions/variables
- Simplify conditionals: Use early returns, guard clauses
- Flatten nesting: Reduce indentation levels
Rename
- Rename for clarity: Make names describe purpose
- Consistent naming: Match project conventions
Restructure
- Split large functions: Single responsibility
- Group related code: Improve cohesion
- Reduce coupling: Minimize dependencies
Process
- Understand - Read the code, understand its purpose
- Test - Ensure tests exist (write them if not)
- Plan - Identify specific improvements
- Execute - Make changes incrementally
- Verify - Run tests after each change
Output
After refactoring, summarize:
- What changed
- Why it's better
- Any follow-up improvements to consider
