rails-toolkit

Perform a comprehensive code review using parallel specialized subagents for security analysis and Rails best practices review. Incorporates previous review decisions to avoid redundant suggestions.

Set up a new git worktree for a Linear issue, creating a separate working directory off the main branch.

Use this agent when working on Ruby on Rails backend code, including models, controllers, services, jobs, database migrations, API endpoints, background processing, or any server-side Ruby logic. This agent should be consulted for: - Implementing new backend features following Rails conventions - Refactoring existing Rails code to improve design - Writing or reviewing service objects, query objects, and form objects - Database schema design and migration creation - ActiveRecord model design and optimization - Background job implementation with Sidekiq - API endpoint design and implementation - Multi-tenant architecture decisions - Performance optimization and N+1 query prevention Examples: <example> Context: User is implementing a new feature for managing project artifacts. user: "I need to create a service object that processes GitHub artifacts and creates traceability links based on similarity scores" assistant: "I'll use the rails-backend-expert agent to design and implement this service object following our project's conventions." <rails-backend-expert agent provides implementation following Result pattern, POODR principles, and project-specific patterns from CLAUDE.md> </example> <example> Context: User has just written a new Rails model. user: "I've added a new ReviewApproval model. Can you review it?" assistant: "Let me use the rails-backend-expert agent to review the model implementation." <rails-backend-expert agent reviews the code, checking for: proper use of acts_as_tenant, timestamp patterns over booleans, Postgres enums, associations, validations, and alignment with project conventions> </example> <example> Context: User is experiencing N+1 query issues. user: "The artifacts index page is really slow" assistant: "I'll use the rails-backend-expert agent to analyze and optimize the query performance." <rails-backend-expert agent identifies N+1 queries, suggests eager loading, and implements optimizations following Rails best practices> </example>

Use this agent when you need expert code review for Ruby on Rails applications, focusing on Rails conventions, POODR principles, and idiomatic Ruby practices. Examples: <example>Context: The user has just implemented a new service object for user registration and wants it reviewed for Rails best practices. user: 'I just created a user registration service. Here's the code: [code snippet]' assistant: 'Let me use the rails-code-reviewer agent to provide expert feedback on your Rails service implementation.' <commentary>Since the user is requesting code review for Rails code, use the rails-code-reviewer agent to analyze the implementation against Rails conventions and POODR principles.</commentary></example> <example>Context: The user has written a complex controller action and wants feedback on whether it follows Rails conventions. user: 'Can you review this controller method? I'm not sure if I'm following Rails best practices: [controller code]' assistant: 'I'll use the rails-code-reviewer agent to analyze your controller implementation for Rails conventions and suggest improvements.' <commentary>The user is asking for Rails-specific code review, so the rails-code-reviewer agent should be used to evaluate the controller against Rails patterns.</commentary></example>

Use this agent when you need to develop new features, implement user stories, or build functionality in a Ruby on Rails application using modern Rails patterns and best practices. This agent excels at TDD-driven development, clean architecture, and Hotwire integration. Examples: - <example> Context: User needs to implement a new user registration feature with email verification. user: "I need to build a user registration system with email verification using Rails and Hotwire" assistant: "I'll use the rails-feature-developer agent to implement this feature following TDD principles and Rails conventions." <commentary> The user is requesting feature development, so use the rails-feature-developer agent to build the registration system with proper testing, service objects, and Hotwire integration. </commentary> </example> - <example> Context: User wants to add real-time notifications to their Rails app. user: "Can you help me add live notifications that update without page refresh?" assistant: "I'll use the rails-feature-developer agent to implement real-time notifications using Hotwire Turbo Streams." <commentary> This is a feature development request that requires Hotwire expertise, making the rails-feature-developer agent the perfect choice. </commentary> </example>

Use this agent when you need to review Ruby on Rails code for security vulnerabilities, ensure proper multi-tenant data isolation with ActsAsTenant, and verify adherence to security best practices. Examples: - <example>Context: The user has just implemented a new controller action that handles sensitive user data. user: "I've added a new endpoint to handle user profile updates. Here's the controller code: [code]" assistant: "Let me use the rails-security-reviewer agent to analyze this code for security vulnerabilities and tenant isolation." <commentary>Since the user is sharing new controller code that handles sensitive data, use the rails-security-reviewer agent to check for security issues, proper tenant scoping, and Rails security best practices.</commentary></example> - <example>Context: The user has modified database queries and wants to ensure tenant separation is maintained. user: "I updated the search functionality to include cross-model queries. Can you check if the tenant scoping is correct?" assistant: "I'll use the rails-security-reviewer agent to verify the tenant isolation and security of these database queries." <commentary>Since the user is asking about tenant scoping in database queries, use the rails-security-reviewer agent to ensure ActsAsTenant is properly implemented and no data leakage is possible.</commentary></example>

This skill should be used when implementing features from Linear issues with full TDD workflow, automated planning, parallel code reviews (security and Rails best practices), systematic feedback implementation, and automated PR creation with Linear integration. Use when the user provides a Linear issue ID (e.g., "TRA-9", "DEV-123") and wants a complete implementation workflow from issue to PR.

This skill should be used when writing, reviewing, or improving RSpec tests for Ruby on Rails applications. Use this skill for all testing tasks including model specs, controller specs, system specs, component specs, service specs, and integration tests. The skill provides comprehensive RSpec best practices from Better Specs and thoughtbot guides.