kieran-rails-reviewer

Review Rails pull requests for regressions, testability, naming, and Turbo Streams.

12|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/jikig-ai/soleur --skill kieran-rails-reviewer-jikig-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kieran-rails-reviewer
Source: https://github.com/jikig-ai/soleur/tree/main/.openhands/skills/kieran-rails-reviewer
Command: npx skills add https://github.com/jikig-ai/soleur --skill kieran-rails-reviewer-jikig-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a high-bar, opinionated Rails code review that finds regressions, convention violations, unclear naming, poor testability, and maintainability risks in both existing code changes and new features.

Core Features & Use Cases

  • Strict existing-code scrutiny: Flag any added complexity in existing files and demand strong justification or extraction to new controllers/services.
  • Pragmatic new-code feedback: Approve isolated, well-scoped additions while suggesting testable improvements and clearer structure.
  • Turbo Streams, naming, and namespacing rules: Enforce inline turbo_stream arrays for simple streams, clear 5-second-readable names, and class Module::ClassName namespacing.
  • Testing and extraction guidance: Evaluate testability, recommend extracting complex logic to services, and call out deletions or regressions that may break workflows.

Quick Start

Ask the agent to review a Rails pull request by providing the diff and requesting a strict review focused on regressions, testability, naming, Turbo Streams, and service extraction.

Frequently Asked Questions about kieran-rails-reviewer

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

FAQPage Schema
How do I perform a strict Rails code review for a pull request?

Perform a strict Rails code review by evaluating the pull request diff for convention violations, regressions, unclear naming, and poor testability. Apply scrutiny to existing code modifications and new features, demanding strong justification or service extraction for added complexity.

What is the best way to enforce naming and namespacing conventions in Rails service extraction?

Enforce naming and namespacing conventions in Rails service extraction by requiring clear, 5-second-readable names and applying strict Module::ClassName namespacing to ensure clarity and maintainability across new services.

How do I review Turbo Streams in Rails to prevent maintainability issues?

Review Turbo Streams in Rails by enforcing inline turbo_stream arrays for simple broadcasts and flagging complex logic for extraction. This prevents maintainability issues and ensures clear, testable view updates.

Does this Rails code review approach flag regressions and deletions in existing code?

Yes, this Rails code review approach actively flags regressions and deletions in existing code. It evaluates testability and calls out modifications that may break workflows, recommending concrete fixes with examples.

When should I extract controller logic to a service in Rails?

Extract controller logic to a service in Rails when added complexity in existing files lacks strong justification. A strict review flags poor testability and maintainability risks, recommending service extraction for isolated, well-scoped code.