rubocop/rails-style-guide resource
A community-driven Ruby on Rails style guide observed · 2026-08-28
Health v2 · maintenance only
74/100
- Activity 93
- Release rhythm 35
- Longevity 100
Flags: no_releases no_license no_readme
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 5456
- days_rel: n/a
- days_push: 44
- n_releases_24m: 0
Adoption not part of the score
6504 stars · 1046 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
A community-driven style guide for Ruby on Rails covering routing, controllers, models, migrations, views, and more. It serves as the reference for the RuboCop Rails cops and documents recommended coding conventions.
Use cases
- how should I structure Rails routes
- best practices for ActiveRecord models
- Rails coding conventions for teams
- style rules for Rails migrations
- how to write skinny controllers in Rails
- recommended Rails style guide for RuboCop
When to choose
- you write Ruby on Rails code and want consistent team conventions
- you use RuboCop Rails and want to understand the rationale behind its cops
- you are onboarding developers to a Rails codebase
When to avoid
- you need executable linting rather than documentation (use rubocop-rails)
- you work outside Ruby or Rails
- you need a machine-readable config rather than prose guidance
Facets
learning-resource · maturity active
documentation web-development developer-tools documentation cross-platform ruby rails style-guide rubocop code-style best-practices
1 source
- homepage: http://rails.rubystyle.guide · fetched 2026-08-29 · 67a2f5601f36
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| rubocop/rails-style-guide | main | 74 |
For agents
markdown · JSON · MCP: product_card(name="rubocop/rails-style-guide")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem