kieran-rails-reviewer

To catch hidden regressions in a Ruby on Rails pull request, apply a strict code review to the diff that flags unnecessary complexity, removed callbacks without preserved behavior, and convention breaks to prevent long-term technical debt.

Enforcing maintainability standards for Rails controllers and models requires flagging overbuilt abstractions, hard-to-test code structures, and Rails clarity failures. A calibrated confidence score prioritizes high-impact issues while suppressing low-value stylistic criticism.

Yes, this Rails code review approach works with Turbo and Hotwire stream changes by flagging unnecessary complexity in stream responses. It identifies when inline render arrays would be simpler than separate templates in your pull request workflows.

Automate flagging unnecessary complexity in Rails service objects by reviewing code diffs for existing-file complexity that adds no value. This strict review catches overbuilt abstractions and hard-to-test code structures to reduce technical debt.

No, you should not use this code review skill for non-Rails Ruby application changes. The conditional review logic activates only when diffs touch Rails application code, specifically controllers, services, models, and Turbo/Hotwire patterns.