rails-conventions

Review Rails 8 codebases for naming, architecture, and security conventions.

17|3|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/ethos-link/rails-conventions --skill rails-conventions-ethos-link
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rails-conventions
Source: https://github.com/ethos-link/rails-conventions/tree/main
Command: npx skills add https://github.com/ethos-link/rails-conventions --skill rails-conventions-ethos-link

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses inconsistencies in Rails 8 codebases by providing comprehensive guidelines for architecture, implementation, and review processes, helping teams maintain high standards in production code.

Core Features & Use Cases

  • Code Consistency: Enforces naming conventions, architecture patterns, and code organization.
  • Implementation Guidance: Offers step-by-step instructions for building and reviewing Rails features.
  • Review Assistance: Assists in reviewing pull requests for security, performance, and testing.
  • Use Case: When implementing a new Rails feature, use this Skill to align the code with established conventions and ensure best practices are followed.

Quick Start

Run the skill to review the codebase for consistency, following the provided guidelines.

Frequently Asked Questions about rails-conventions

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

FAQPage Schema
How do I enforce Ruby on Rails 8 code conventions during a pull request review?

You can enforce Rails 8 code consistency by applying architectural and implementation guidelines to review naming, layering, Active Record models, controllers, and background jobs against established best practices.

What are the key architectural layering conventions for a Rails 8 application?

Key Rails 8 architectural conventions involve strict separation between models, controllers, routes, and background jobs, ensuring code organization follows 37signals-inspired style profiles for maintainable production code.

Do I need to know Hotwire and Active Job to use Rails 8 implementation guidance?

Yes, applying Rails 8 architectural and implementation guidance requires existing knowledge of Active Record, Active Job, Hotwire, and related conventions to effectively review and align production code.

What is the best way to standardize Active Record models and controllers in Rails 8?

The best way to standardize Active Record models and controllers in Rails 8 is to apply 37signals-inspired style profiles and local conventions, checking naming, performance, and security during implementation.

When should I check background jobs and security conventions in my Rails codebase?

You should check background jobs and security conventions when implementing new Rails 8 features or reviewing pull requests, ensuring Active Job performance and code quality align with established guidelines.