Refactoring Agents

Refactoring agents restructure code across multiple files while preserving behavior, making them useful for large-scale migrations, API updates, and codebase modernization tasks that would take a human developer days or weeks. They appear after code review agents in the sequence because you review first to understand what needs to change, then automate the change; skipping review means the agent refactors without a shared understanding of which patterns are intentional and which are the actual problems. The critical dependency is test coverage: without a strong test suite, you have no way to verify the agent's changes are safe, which is why test generation is a natural prerequisite for any refactoring workflow you plan to hand off to an agent.