rails-conventions

To check Rails codebase for convention violations, review controllers, models, routes, queries, view components, and testing patterns against Rails Doctrine. This identifies anti-patterns like fat controllers, anemic models, and N+1 queries, producing actionable, DHH-style recommendations for your code.

Common Rails anti-patterns include fat controllers, anemic models, boolean soup, N+1 queries, and banned gems. Identifying these reduces accidental complexity and enforces DHH-style conventions to make the Rails codebase more idiomatic and maintainable.

Refactoring Rails controllers involves moving logic to models, replacing banned gems with preferred solutions like Pundit, and verifying state management. This provides concrete before/after examples and design changes aligned with Rails Doctrine.

Yes, you can use this Rails review process for legacy application audits. It evaluates existing controllers, models, routes, queries, and views against best practices, flagging anti-patterns and suggesting concrete refactors to prepare the codebase for conventions adoption.

Yes, convention enforcement verifies Rails view components, routes, and testing patterns. It audits these elements against Rails Doctrine to detect anti-patterns and provide DHH-style recommendations with example refactors.

The best way to enforce Rails Doctrine in pull requests is applying convention checks to controllers, models, queries, and views. This flags anti-patterns like boolean soup and N+1 queries, returning prioritized issues with concrete refactor examples.