dhh-rails-reviewer

Analyze Rails codebases for convention violations and anti-patterns.

2|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/CristoVentures/LocalCents --skill dhh-rails-reviewer-cristoventures
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dhh-rails-reviewer
Source: https://github.com/CristoVentures/LocalCents/tree/main/.agent/skills/dhh-rails-reviewer
Command: npx skills add https://github.com/CristoVentures/LocalCents --skill dhh-rails-reviewer-cristoventures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The DHH Rails reviewer helps teams identify Rails-convention violations, anti-patterns, and architectural decisions that violate Rails philosophy, delivering crisp, opinionated feedback to keep Rails apps lean and maintainable.

Core Features & Use Cases

  • Rails Convention Adherence: highlights breaks from Rails conventions, promotes RESTful design, skinny controllers, and fat models.
  • Pattern Recognition: detects non-Rails patterns like unnecessary API layers, unrelated JavaScript patterns, or over-abstracted service layers.
  • Complexity Analysis: challenges over-engineered solutions such as excessive decorators, service objects, or event sourcing in standard CRUD apps.
  • Use Case: when reviewing a recently implemented feature, it exposes deviations and prescribes the Rails way.

Quick Start

Describe the Rails code you want reviewed and I will deliver a brutally honest, Rails-centric critique in the DHH voice.

Frequently Asked Questions about dhh-rails-reviewer

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

FAQPage Schema
How do I check if my Rails code follows convention over configuration?

To check Rails convention adherence, analyze your codebase for anti-patterns like skinny controllers and fat models violations, ensuring RESTful design and lean architecture. The review identifies deviations from Rails philosophy and highlights unnecessary abstractions.

What is the best way to review a Rails feature implementation for over-engineering?

The best way to review Rails features for over-engineering is to challenge excessive decorators, service objects, or event sourcing in standard CRUD apps. This analysis exposes non-Rails patterns and prescribes the Rails way to keep applications maintainable.

Can I use a Rails code review to detect unnecessary API layers?

Yes, you can use a Rails code review to detect unnecessary API layers and unrelated JavaScript patterns. The analysis identifies non-Rails architectural decisions and delivers opinionated feedback to align your application with Rails conventions.

How do I get actionable feedback on my Rails architectural plan?

To get actionable feedback on Rails architectural plans, provide clear code samples or descriptions of your goals. The review applies Rails principles to your architectural decisions and delivers crisp critiques to keep your app lean.

When should I not use service objects in a Rails application?

You should not use service objects in Rails applications when they over-abstract standard CRUD operations. The review challenges over-engineered solutions like excessive service layers, promoting convention over configuration for maintainable code.