rails-best-practices

Rails code review identifies anti-patterns, security vulnerabilities, and performance bottlenecks across controllers, models, views, and migrations. Submit your code and receive specific suggestions on Time.zone.now usage, N+1 query prevention, strong parameters, and other Rails conventions to improve efficiency and maintainability.

Common Rails anti-patterns include using default_scope, missing save checks, N+1 queries, improper timezone handling, weak parameter validation, and inadequate documentation. This skill enforces standards for controllers, models, views, and migrations to prevent bugs and security vulnerabilities during code review and generation.

Yes, guided code generation creates new Rails controllers, models, and migrations that automatically adhere to established conventions and best practices. Generated code follows standards for strong parameters, timezone handling, performance optimization, and security from the outset.

N+1 query prevention is enforced during code review by analyzing controller and model code for inefficient database access patterns. The skill identifies missing eager-loading opportunities and suggests optimizations to improve query performance across your Rails application.

Rails best practice enforces Time.zone.now instead of Time.now to respect application timezone settings. During code review and generation, timezone handling is automatically validated to ensure consistent, timezone-aware datetime operations throughout your codebase.