= RuboCop

[,Officer Alex J. Murphy / RoboCop]
____
Role models are important.
____

== Overview

*RuboCop* is a Ruby static code analyzer (a.k.a. linter) and code
formatter. Out of the box it will enforce many of the guidelines
outlined in the community https://rubystyle.guide[Ruby Style Guide].

RuboCop packs a lot of features on top of what you'd normally expect from a
linter:

* Works with every major Ruby implementation
* Autocorrection of many of the code offenses it detects
* Robust code formatting capabilities
* Multiple result formatters for both interactive use and for feeding data into other tools
* Ability to have different configuration for different parts of your codebase
* Ability to disable certain cops only for specific files or parts of files
* Extremely flexible configuration that allows you to adapt RuboCop to pretty much every style and preference
* It's easy to extend RuboCop with custom cops and formatters
* A vast number of ready-made xref:plugins.adoc[plugins] (e.g. `rubocop-rails`, `rubocop-rspec`, `rubocop-performance` and `rubocop-minitest`)
* Built-in xref:usage/lsp.adoc[Language Server Protocol (LSP)] and xref:usage/mcp.adoc[Model Context Protocol (MCP)] support
* Wide editor/IDE support via LSP
* Many online services use RuboCop internally (e.g. CodeClimate and Codacy)
* Best logo/stickers ever

The project is closely tied to several efforts to document and promote the best practices of the Ruby community:

* https://rubystyle.guide/[Ruby Style Guide]
* https://rails.rubystyle.guide/[Rails Style Guide]
* https://rspec.rubystyle.guide/[RSpec Style Guide]
* https://minitest.rubystyle.guide/[Minitest Style Guide]

A long-term goal of RuboCop (and its core extensions) is to cover with cops all the guidelines from the community style guides.

== Philosophy

Early on RuboCop aimed to be an opinionated linter/formatter that adhered very closely to the Ruby Style Guide (think `gofmt` and the like).
In those days cops supported just a single style and you couldn't even turn individual cops off. Eventually, we realized
that in the Ruby community there were so many competing styles and preferences that it was going to be really
challenging to find one set of defaults that makes everyone happy. Part of this was Ruby's own culture and philosophy,
part was the lack of common standards for almost 20 years. It's hard to undo any of those, but it's also not really necessary.

The early feedback we got led us to adopt a philosophy of (extreme) configurability and flexibility, and trying to account for every _common_ style
of programming in Ruby. While we still believe that there's a lot of merit to just sticking to the community
style guides, we acknowledge that Ruby is all about diversity and doing things the way that makes you happy. Whatever
style preferences you have RuboCop is there for you. That's our promise and our guarantee. Within the subjective limits of sanity that is.

== Next Steps

So, what to do next? While you can peruse the documentation in whatever way you'd like, here are
a few recommendations:

* Start with the xref:usage/getting_started.adoc["Getting Started"] guide to get up and running quickly.
* See xref:usage/cli_reference.adoc["CLI Reference"] for the full command-line reference.
* Adjust RuboCop to your style/preferences. RuboCop is an extremely flexible tool and most aspects of its behavior
can be tweaked via various https://github.com/rubocop/rubocop/blob/master/config/default.yml[configuration
options]. See xref:configuration.adoc["Configuration"] for more details.
* See xref:versioning.adoc["Versioning"] for information about RuboCop versioning,
updates, and the process of introducing new cops.
* Explore the xref:plugins.adoc[available plugins].
