dhh-rails-reviewer

Rails code review for convention over configuration violations identifies deviations like fat models or non-RESTful routes and critiques unnecessary abstractions to promote simplicity in the majestic monolith.

Common anti-patterns when adding JavaScript frameworks to a Ruby on Rails application include building unnecessary API layers, implementing JWT tokens, and applying Redux-style state management instead of using Rails conventions.

Your Rails app does not need service objects and presenters for handling complex logic if you follow the majestic monolith approach, which critiques these unnecessary abstractions in favor of convention over configuration.

Checking if a new Rails feature follows DHH's best practices involves analyzing the code for adherence to Rails conventions, detecting JavaScript framework infiltration, and tearing apart unnecessary complexity like separate API layers.

You should avoid using hexagonal architecture in Ruby on Rails when it introduces unnecessary complexity that deviates from the majestic monolith philosophy and contradicts the principle of convention over configuration.