rubocop-fixer
Use when fixing Rubocop violations. Runs Rubocop to identify issues, applies fixes following project conventions, and explains non-obvious corrections.
When & Why to Use This Skill
The Rubocop Fixer is a specialized Claude skill designed to automate code quality enforcement in Ruby and Rails projects. It streamlines the development workflow by identifying linting violations, applying project-specific style corrections, and providing educational explanations for complex refactoring. By integrating static analysis with intelligent fixing, it ensures codebase consistency, reduces technical debt, and helps developers adhere to community best practices and custom configurations.
Use Cases
- Automated Style Alignment: Quickly resolve common Ruby style violations such as string literal preferences, frozen string literal comments, and line length issues across multiple files.
- Complexity Refactoring: Identify and refactor methods with high ABC (Assignments, Branches, Conditions) metrics or excessive length into modular, maintainable code blocks.
- Rails-Specific Optimization: Ensure ActiveRecord associations follow best practices, including the enforcement of 'dependent' options and 'inverse_of' definitions to prevent data integrity issues.
- Legacy Codebase Cleanup: Manage large-scale technical debt by generating '.rubocop_todo.yml' files and incrementally applying fixes to modernize older Ruby applications.
- Code Review Pre-processing: Use as a pre-review tool to automatically handle trivial formatting and convention issues, allowing human reviewers to focus on logic and architecture.
| name | rubocop-fixer |
|---|---|
| description | Use when fixing Rubocop violations. Runs Rubocop to identify issues, applies fixes following project conventions, and explains non-obvious corrections. |
| allowed-tools | Read, Write, Edit, Bash, Grep, Glob |
Rubocop Fixer
You fix Rubocop violations in Rails projects while respecting project-specific configurations.
Process
1. Check Configuration
First, understand the project's Rubocop setup:
# Check for config file
cat .rubocop.yml
# Check inherited configs
cat .rubocop_todo.yml 2>/dev/null
2. Run Rubocop
# All violations
bundle exec rubocop
# Specific file
bundle exec rubocop app/models/user.rb
# Specific cop
bundle exec rubocop --only Style/StringLiterals
# Auto-correct safe violations
bundle exec rubocop -a
# Auto-correct all (including unsafe)
bundle exec rubocop -A
3. Understand the Violation
Before fixing, understand why the cop exists:
# Show cop documentation
bundle exec rubocop --show-cops Style/StringLiterals
Common Violations & Fixes
Style/StringLiterals
# Before (violation)
name = "hello"
# After (if configured for single quotes)
name = 'hello'
# Note: Use double quotes when interpolation or escapes needed
name = "hello #{user}"
Style/FrozenStringLiteralComment
# Add at top of file
# frozen_string_literal: true
class User
# ...
end
Layout/LineLength
# Before (too long)
def very_long_method_name(first_parameter, second_parameter, third_parameter, fourth_parameter)
# After
def very_long_method_name(
first_parameter,
second_parameter,
third_parameter,
fourth_parameter
)
Style/Documentation
# Before (missing documentation)
class UserService
end
# After
# Handles user-related business logic including registration
# and profile management.
class UserService
end
# Or disable for specific class
class UserService # rubocop:disable Style/Documentation
end
Metrics/MethodLength
# Before (too long)
def process_order
validate_items
calculate_subtotal
apply_discounts
calculate_tax
calculate_shipping
finalize_total
create_invoice
send_confirmation
update_inventory
notify_warehouse
end
# After (extract methods)
def process_order
prepare_order
complete_order
post_order_tasks
end
private
def prepare_order
validate_items
calculate_totals
end
def calculate_totals
calculate_subtotal
apply_discounts
calculate_tax
calculate_shipping
finalize_total
end
def complete_order
create_invoice
send_confirmation
end
def post_order_tasks
update_inventory
notify_warehouse
end
Metrics/AbcSize
ABC = Assignments, Branches, Conditions
# Before (high ABC)
def process(user)
if user.active?
user.name = params[:name]
user.email = params[:email]
user.role = params[:role]
user.save!
notify(user)
end
end
# After (lower ABC)
def process(user)
return unless user.active?
update_user_attributes(user)
user.save!
notify(user)
end
def update_user_attributes(user)
user.assign_attributes(user_params)
end
def user_params
params.slice(:name, :email, :role)
end
Rails/HasManyOrHasOneDependent
# Before
has_many :posts
# After
has_many :posts, dependent: :destroy
# or
has_many :posts, dependent: :nullify
Rails/InverseOf
# Before
has_many :posts
belongs_to :user
# After
has_many :posts, inverse_of: :user
belongs_to :user, inverse_of: :posts
Inline Disabling
When a violation is intentional:
# Disable for line
some_code # rubocop:disable Style/SomeCop
# Disable for block
# rubocop:disable Style/SomeCop
some_code
more_code
# rubocop:enable Style/SomeCop
# Disable for file (at top)
# rubocop:disable Style/SomeCop
Generating TODO File
For legacy codebases with many violations:
# Generate .rubocop_todo.yml with all current violations
bundle exec rubocop --auto-gen-config
# Then incrementally fix cops
bundle exec rubocop --only Style/StringLiterals -a
Output Format
After fixing violations:
- Violations Fixed - List of cops and count
- Manual Fixes - Changes requiring human judgment
- Remaining - Violations that need review
- Verification -
bundle exec rubocopoutput