dhh-rails-reviewer

Analyze Rails codebases to enforce Rails conventions in code reviews.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/drhazemibclc/plate --skill dhh-rails-reviewer-drhazemibclc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dhh-rails-reviewer
Source: https://github.com/drhazemibclc/plate/tree/main/.codex/skills/dhh-rails-reviewer
Command: npx skills add https://github.com/drhazemibclc/plate --skill dhh-rails-reviewer-drhazemibclc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DHH Rails reviewer helps teams ensure Rails conventions are followed, avoiding overengineered patterns and React-like layers in a Rails app.

Core Features & Use Cases

  • Brutally honest Rails code reviews that enforce convention over configuration and identify fat models, skinny controllers, and inappropriate abstractions.
  • Detect deviations such as unnecessary API layers, external services, or misused design patterns, and propose Rails-native alternatives.
  • Use in code reviews of controllers, models, service objects, and architecture decisions to keep Rails apps simple, maintainable, and monolithic.

Quick Start

Provide the Rails codebase you want reviewed, and I'll return an opinionated DHH-style critique.

Frequently Asked Questions about dhh-rails-reviewer

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

FAQPage Schema
How do I enforce Rails conventions in a code review?

To enforce Rails conventions in a code review, analyze the codebase for anti-patterns, unnecessary API layers, and JavaScript framework contamination. It provides structured feedback to identify deviations from Rails philosophy and recommend Rails-native alternatives for controllers, models, and services.

What are common Rails anti-patterns to look for in controllers and models?

Common Rails anti-patterns include fat models, skinny controllers violations, and inappropriate abstractions like unnecessary API layers. Detecting these deviations helps avoid overengineered patterns and React-like layers, proposing Rails-native alternatives to keep the application maintainable and monolithic.

How do I identify unnecessary abstractions in a Rails app?

Identify unnecessary abstractions in a Rails app by evaluating service objects and architecture for misused design patterns and unnecessary API layers. An opinionated critique highlights these overengineered patterns, recommending Rails-native alternatives to keep the monolithic architecture simple.

Does this approach work for reviewing Rails monolith architecture?

Yes, this approach works for reviewing Rails monolith architecture by evaluating architecture decisions against Rails conventions. It identifies JavaScript framework contamination and overengineered patterns, proposing Rails-native alternatives to keep the monolithic application simple and maintainable.

When should I avoid adding service objects in Rails?

You should avoid adding service objects in Rails when they create unnecessary abstractions or React-like layers. Code reviews focused on Rails conventions identify these deviations and recommend Rails-native patterns to keep the monolithic architecture simple and maintainable.