Refactor: $ARGUMENTS
Rules
- NEVER change behavior — only improve structure
- ALWAYS run tests before AND after
- Make small, incremental changes
- Each change should be independently verifiable
Steps
Run tests first — establish baseline
[test command]If tests fail BEFORE refactoring, STOP and tell the user.
Read the code to refactor and understand it fully
Read the tests for this code — understand what behavior is expected
Identify refactoring opportunities:
- Extract method (function too long)
- Extract variable (complex expression)
- Rename for clarity
- Remove duplication (DRY)
- Simplify conditionals
- Replace magic numbers with constants
- Reduce nesting depth
- Split large files
- Improve type safety
Apply changes incrementally
- One refactoring at a time
- Run tests after each change
- If tests fail, revert immediately
Run full test suite
[test command]Report
## Refactoring Summary ### Changes - [what was refactored and why] ### Before → After - [specific improvements] ### Tests - All [X] tests passing - No behavior changes