dhh-rails-reviewer

To catch Rails anti-patterns in a pull request, review the diff to identify non-idiomatic code that fights framework conventions. This process flags unnecessary complexity like over-abstraction or replacing standard sessions with custom JWT auth, ensuring code aligns with Rails' opinionated omakase design.

Common Ruby on Rails anti-patterns include replacing Turbo Hotwire with custom client-side state machines, introducing service layers that merely wrap Active Record behavior, and unnecessary monolith splitting for single-app concerns. These patterns introduce unnecessary complexity and deviate from Rails conventions.

Reviewing Rails code for unnecessary abstractions involves checking if new architectural choices hide core framework functionality. Evaluate pull request diffs to identify over-abstraction that conflicts with Rails' design, assigning confidence levels to distinguish explicit anti-patterns from debatable architectural choices.

This code review approach suppresses low-confidence philosophical complaints by applying calibrated confidence scoring. It evaluates architectural choices and frontend patterns, delivering DHH-aligned review findings that exclusively flag high-confidence anti-patterns deviating from Rails' opinionated design.

You should not use custom JWT authentication in a Rails monolith when it replaces standard sessions unnecessarily. Replacing built-in session management with custom JWT auth is flagged as a high-confidence anti-pattern that introduces unnecessary complexity and fights the framework's omakase design.