dhh-rails-reviewer

Review Rails code and architecture for convention violations and unnecessary complexity.

12|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/jikig-ai/soleur --skill dhh-rails-reviewer-jikig-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dhh-rails-reviewer
Source: https://github.com/jikig-ai/soleur/tree/main/.openhands/skills/dhh-rails-reviewer
Command: npx skills add https://github.com/jikig-ai/soleur --skill dhh-rails-reviewer-jikig-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a blunt, expert Rails-focused code and architecture review that exposes deviations from Rails conventions, unnecessary abstractions, and patterns borrowed from JavaScript frameworks that do not suit Rails applications.

Core Features & Use Cases

  • Convention Policing: Ruthlessly identifies violations of Rails conventions such as fat models, skinny controllers, non-RESTful routing, and repository patterns replacing ActiveRecord.
  • Architecture & Complexity Audit: Flags unnecessary service objects, presenters, event sourcing, microservices, or frontend-driven patterns that increase maintenance and degrade developer happiness.
  • Practical Recommendations: Suggests Rails-centric alternatives (model methods, helpers, sessions, server-side rendering, Hotwire) with attention to performance, maintainability, and onboarding.
  • Use Case: Use it to review a pull request, audit a proposed microservice split, or critique a codebase that mixes heavy JS-framework practices with Rails.

Quick Start

Ask the agent to perform a DHH-style Rails review of your repository and highlight convention violations, unnecessary abstractions, and recommended Rails-centric fixes.

Frequently Asked Questions about dhh-rails-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a Rails pull request for convention violations and unnecessary abstractions?

To review a Rails pull request for convention violations, analyze the code for fat models, skinny controllers, and non-RESTful routing. Flag unnecessary service objects and over-abstracted patterns, recommending Rails-centric alternatives like model methods or helpers to reduce maintenance.

What are common signs of unnecessary complexity in a Rails architecture?

Unnecessary complexity in Rails architecture often appears as service objects, event sourcing, microservices, or heavy JavaScript framework patterns. These deviations from Rails conventions degrade developer happiness and increase maintenance compared to monolith, server-rendered, Hotwire-driven approaches.

When should I use service objects instead of Rails model methods?

Service objects should generally be avoided when a Rails model method or helper can accomplish the task. A Rails architecture review identifies when service objects become unnecessary abstractions that threaten Rails idioms, recommending model methods to maintain developer happiness and onboarding.

Does my Rails app need a microservice split or should I keep a monolith architecture?

Evaluating a microservice split against a monolith architecture involves auditing proposed service boundaries for unnecessary complexity. A Rails-centric review flags microservices that threaten monolith architecture, recommending server-rendering and Hotwire to maintain performance and developer happiness.

How do I audit a Rails codebase for JavaScript framework patterns that don't fit?

To audit a Rails codebase for misfit JavaScript framework patterns, review the code for frontend-driven abstractions replacing server-rendering. Identify patterns increasing maintenance burden and recommend Rails-centric alternatives like Hotwire, sessions, and server-side rendering to restore Rails idioms.