Fix RuboCop workflow issues and warnings

[justin808]

Summary

Fixes RuboCop workflow issues and eliminates warnings for cleaner development experience.

Issues Fixed

1. Eliminated suggestion warnings: Added SuggestExtensions: false to disable unnecessary rubocop-capybara/factory_bot/rspec_rails suggestions
2. Ruby 3.5+ compatibility: Added benchmark, logger, ostruct gems to silence deprecation warnings about gems moving out of stdlib
3. Cleaner RuboCop output: No more tip messages or warnings during execution

Changes

• Updated .rubocop.yml: Added SuggestExtensions: false
• Updated Gemfile.development_dependencies: Added benchmark, logger, ostruct gems for Ruby 3.5+ compatibility

Before

138 files inspected, no offenses detected

Tip: Based on detected gems, the following RuboCop extension libraries might be helpful:
  * rubocop-capybara (https://rubygems.org/gems/rubocop-capybara)
  * rubocop-factory_bot (https://rubygems.org/gems/rubocop-factory_bot)
  * rubocop-rspec_rails (https://rubygems.org/gems/rubocop-rspec_rails)

/Users/justin/.asdf/installs/ruby/3.4.3/lib/ruby/gems/3.4.0/gems/rubocop-1.61.0/exe/rubocop:14: warning: benchmark was loaded from the standard library...

After

138 files inspected, no offenses detected

Benefits

• ✅ Clean RuboCop execution without distracting warnings
• ✅ Forward compatibility with Ruby 3.5+
• ✅ Better developer experience during linting
• ✅ Maintains all existing functionality and test coverage

Testing

• All RuboCop checks pass cleanly without warnings
• All existing RSpec tests continue to pass
• Pre-commit and pre-push hooks work correctly

🤖 Generated with Claude Code

---

This change is 

[coderabbitai]

Warning

Rate limit exceeded

@justin808 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 15 minutes and 25 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 7ef65c1 and 7f3bf29.

⛔ Files ignored due to path filters (1)

• Gemfile.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• .rubocop.yml (1 hunks)
• Gemfile.development_dependencies (1 hunks)

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/rubocop-workflow-improvements

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[claude]

Code Review

Thank you for this PR to improve the RuboCop workflow and eliminate warnings! Here is my review:

✅ Strengths

• Good housekeeping: Eliminating development warnings improves developer experience
• Forward compatibility: Proactively addressing Ruby 3.5+ deprecations is excellent
• Clear documentation: The PR description clearly explains the problem and solution
• Non-breaking changes: These are development-only dependencies that do not affect gem users

📋 Code Quality & Best Practices

1. .rubocop.yml change

✅ Adding SuggestExtensions: false is appropriate since these extensions are not needed for the project.

2. Gemfile.development_dependencies additions

The added gems (benchmark, logger, ostruct) are correctly:

• ✅ Added to development/test group only
• ✅ Set with require: false to avoid auto-loading
• ✅ Properly commented to explain their purpose

🔍 Suggestions for Improvement

1. Consider version constraints: While not critical, you might want to add version constraints for the new gems to ensure compatibility:

   gem "benchmark", "~> 0.4", require: false
   gem "logger", "~> 1.7", require: false  
   gem "ostruct", "~> 0.6", require: false

2. Documentation update: Consider adding a note in CLAUDE.md or the development docs about these gems being required for Ruby 3.5+ compatibility, so future contributors understand why they are there.

✅ Security & Performance

• No security concerns - these are standard Ruby stdlib gems
• No performance impact - gems are development-only with require: false

✅ Test Coverage

• Changes do not affect functionality, so existing tests are sufficient
• PR author confirmed all tests pass without warnings

🎯 Overall Assessment

This is a clean, focused PR that improves the development experience. The changes are minimal, well-documented, and follow the project conventions per CLAUDE.md (especially the RuboCop requirements). Approved! 👍

The only minor suggestion would be to consider adding version constraints for future maintainability, but this is not blocking.