Extract Rails business logic into service objects, concerns, and query objects.
npx skills add https://github.com/fabn/claude-plugins --skill rails-refactor
Please help me install this Agent Skill. Skill: rails:refactor Source: https://github.com/fabn/claude-plugins/tree/main/plugins/rails/skills/refactor Command: npx skills add https://github.com/fabn/claude-plugins --skill rails-refactor
Identifies fat controllers, god models, repeated query chains, complex form handling, and display logic in Ruby on Rails projects and provides structured extraction patterns to reduce complexity, improve testability, and enforce single responsibility.
Ask to refactor OrdersController#create by extracting an OrderCreationService, list files to create and modify, and provide the before/after code changes.
High-intent search queries and answers about installing and using this skill.
Refactoring fat Ruby on Rails controllers involves extracting business logic into focused service objects. This reduces controller complexity by moving validation, payment, and notification processes into separate, testable classes following project initialization and call conventions.
Extract concerns from Rails models over 200 lines when you need to isolate cohesive behavior into ActiveSupport::Concern modules. This separation enforces single responsibility, improves clarity, and enhances reuse across your application without cluttering the main model definition.
The best way to handle repeated query chains in Ruby on Rails is extracting them into query objects. This pattern replaces complex, duplicated ActiveRecord queries with focused, testable classes that encapsulate specific data retrieval logic.
Manage multi-model forms in Rails by encapsulating the complex form handling logic into form objects. This pattern separates form validation and submission processing from controllers, creating a dedicated, testable abstraction for multi-model interactions.
Yes, you can move Rails display logic into DelegateClass wrappers or presenters. This approach extracts view-specific formatting and presentation code from models and controllers, enforcing single responsibility and keeping business logic separated from display concerns.
Yes, you need to update or create specs when extracting service objects from Rails controllers. Running affected test suites and linting new code ensures the extracted abstractions preserve original behavior and maintain testability throughout the refactoring process.
Ouro-labsApply DHH Rails conventions to Ruby and Rails codebases and reviews.
SnakeORestructure Rails codebases by extracting business logic into service objects, concerns, and query objects.
nschnebleCreate Rails service objects with RSpec tests and Result objects.
ThibautBaissacGenerate Rails concerns with accompanying RSpec specs for models and controllers.
