dhh-rails-reviewer

Review Ruby on Rails code by analyzing it against DHH's philosophies, enforcing fat models, skinny controllers, and RESTful routes while rejecting unnecessary complexity. It identifies deviations from the majestic monolith approach and suggests idiomatic Rails solutions.

Common Rails anti-patterns include building unnecessary API layers, using JWTs instead of traditional sessions, and importing Redux-style state management. These JavaScript-centric patterns violate the majestic monolith philosophy and overcomplicate Rails applications.

Yes, you can check if Rails service objects are over-engineered. The review identifies unnecessary abstractions and critiques service objects that could be replaced by idiomatic model methods, ensuring simplicity and adherence to Rails conventions.

The best way to ensure a Rails feature follows the majestic monolith philosophy is to evaluate it for unnecessary abstractions and JavaScript-centric patterns. It checks for convention adherence, suggesting idiomatic Rails solutions over separate API layers.

You should not use service objects in Ruby on Rails applications when the logic could be a model method. The review tears down unnecessary abstractions and over-engineered patterns that deviate from fat models and convention over configuration.