rails-refactorer

Refactor Rails code by applying test-driven changes: extract service objects, isolate controller actions, and update tests in parallel to maintain coverage. Run your test suite after each refactor to ensure functionality remains intact and coverage doesn't drop.

Sandi Metz rules enforce clean code: classes under 100 lines, methods under 5 lines, no more than 4 parameters per method, and single responsibility. They improve Rails maintainability by reducing complexity and making controllers thin and models focused.

Identify a long method in your model, move its logic into a dedicated service class, call that service from the model, and write tests for both layers. This isolates business logic, reduces model bloat, and follows Rails conventions for cleaner architecture.

Yes. Refactor Rails code safely by preserving test coverage throughout: maintain existing test suites, add tests for extracted components, use strong parameters and guard clauses, and verify all tests pass after each change to catch regressions immediately.

Key patterns include extracting service objects for business logic, isolating custom actions into dedicated controllers, adding semantic scopes, using before_action filters properly, and renaming associations for clarity. Each follows Rails idioms and reduces complexity while maintaining test coverage.

Refactor controllers when they handle multiple responsibilities—extract actions into dedicated controllers and move business logic into service objects. Refactor models when methods exceed 5 lines or violate single responsibility—extract into services or scopes to keep models thin and focused.