Rails Code Review (The Rails Way)

When reviewing Rails code, analyze it against the following areas. When writing new code, follow rails-code-conventions (principles, logging, path rules) and rails-stack-conventions (stack-specific UI and Rails patterns).

Core principle: Review early, review often. Self-review before PR. Re-review after significant changes.

Pre-flight Checks

Before starting the review, verify the following:

• Rails project detected: Confirm you're in a Rails application (check for config/application.rb, Gemfile with rails, or bin/rails)
• Diff available: Ensure you have access to the code changes (git diff, PR diff, or file paths)
• Files exist: Verify all files referenced in the diff exist in the repository
• Review scope clear: Confirm whether reviewing a full PR, a specific feature, or targeted files

If pre-flight checks fail:

• Not a Rails project → Use appropriate review skill for the technology stack
• No diff available → Request the diff or file paths from the user
• Files missing → Flag as Critical and request clarification before proceeding