rails-review

Review Rails code against team house conventions with prioritized findings.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/hschne/pi-stuff --skill rails-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rails-review
Source: https://github.com/hschne/pi-stuff/tree/main/skills/rails-review
Command: npx skills add https://github.com/hschne/pi-stuff --skill rails-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates vague, unactionable Rails code reviews that fail to catch violations of team-specific coding conventions, reducing time spent on back-and-forth feedback and ensuring long-term codebase consistency.

Core Features & Use Cases

  • Convention-Aligned Review Logic: Evaluates Rails diffs, pull requests, individual controller/model files, and recent code changes against your team's defined house conventions, rather than generic one-size-fits-all best practices.
  • Prioritized Actionable Findings: Ranks all identified issues by predefined severity (correctness, security, maintainability, performance, style) and provides concrete replacement code with exact file:line references for every violation.
  • Anti-Pattern Detection: Automatically flags common Rails anti-patterns including service object overuse, business logic in controllers, missing database constraints, unscoped tenant lookups, and unnecessary metaprogramming.
  • Real-World Use Case: Your team has a strict rule against business logic in controllers. When you submit a PR with a controller action that handles multi-record order writes, this Skill will flag the violation and suggest moving the logic to a model or concept-named PORO per your team's rules.

Quick Start

Request a rails review of the open pull request for your Rails e-commerce app's checkout flow.

Frequently Asked Questions about rails-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce team coding conventions during a Rails code review?

Enforce team coding conventions by evaluating Rails pull requests and individual controller or model diffs against your defined house rules, generating prioritized, actionable findings with concrete code replacements.

How do I detect Rails anti-patterns in a pull request?

Detect Rails anti-patterns by analyzing pull request diffs to automatically flag issues like service object overuse, business logic in controllers, missing database constraints, and unscoped tenant lookups.

What is the best way to flag business logic in Rails controllers?

The best way to flag business logic in Rails controllers is to review controller actions against team standards, catching multi-record writes or complex logic and suggesting a move to models or concept-named POROs.

Can I review individual Rails model files for missing database constraints?

Yes, you can review individual Rails model files for missing database constraints by analyzing the code changes and providing actionable findings with exact file and line references for every violation.

Why does my Rails code review fail to catch violations of our house conventions?

Your Rails code review may fail to catch house convention violations if it relies on generic best practices instead of applying opinionated rules tailored to your team's specific layering, abstraction, and testing standards.