rails-cto

Companion Ruby gem to the rails-cto Claude plugin. Bundles the quality toolchain the plugin's skills depend on (RuboCop, Reek, Flog, Flay, Brakeman, bundler-audit, SimpleCov, Herb) and ships matching configuration templates you can drop into any Rails app with a single command.

Add to your Gemfile:

group :development, :test do
  gem "rails-cto"
  gem "rubocop-rails", require: false  # optional companion — see note below
end

Note on rubocop-rails: it is not a hard dependency of rails-cto because it transitively pulls in activesupport (and connection_pool), which can conflict with host-app pins. The bundled .rubocop.yml still references plugins: - rubocop-rails, so add it to your own Gemfile if you want the Rails cops. Drop that line from your .rubocop.yml if you don't.

Then:

bundle install
bundle exec rails-cto init

• Copies config templates into your project (skipping any that already exist):
  • .rubocop.yml
  • .reek.yml
  • .bundler-audit.yml
  • config/brakeman.yml
  • .herb/rewriters/align-attributes.mjs
  • .herb/rules/no-inline-styles.mjs
• Patches test/test_helper.rb to boot SimpleCov with the JSON formatter (so the plugin's QA skill can read coverage/coverage.json).
• Appends a short block to CLAUDE.md telling Claude Code this project uses the rails-cto plugin.

Pass --force to overwrite existing files.

The bundled .rubocop.yml auto-enables this cop. It enforces the mandatory Minitest::Spec subject rule from the plugin:

• Every *_test.rb class must define subject { ... } exactly once at the top of the class.
• subject must not be reassigned inside nested describe/it blocks.

Disable per file with a standard RuboCop comment:

# rubocop:disable RailsCTO/MinitestSubject

• Claude plugin: https://github.com/mattsears/rails-cto
• Gem source: https://github.com/mattsears/rails-cto-gem

MIT.