37signals-review

Review Rails code against 37signals conventions and patterns.

1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/joshyorko/agent-skills --skill 37signals-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 37signals-review
Source: https://github.com/joshyorko/agent-skills/tree/main/plugins/rails-37signals-patterns/skills/37signals-review
Command: npx skills add https://github.com/joshyorko/agent-skills --skill 37signals-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reviews Rails code for adherence to 37signals Rails patterns and conventions, identifying architectural drift, anti-patterns, and opportunities for improvement.

Core Features & Use Cases

  • Detects CRUD philosophy violations, service-object patterns, boolean flags vs state records, and multi-tenant concerns; provides concrete, actionable refactors aligned with 37signals styles.
  • Guides architecture audits, refactors, and code reviews to maintain consistency across Rails projects, with a structured feedback format and escalation via related skills like $37signals-model, $37signals-concerns, and $37signals-turbo.
  • Returns prioritized recommendations with severity and rationale, ensuring engineers can implement changes quickly and safely.

Quick Start

Run a code review on a Rails project to receive a prioritized list of improvements and architectural guidance.

Frequently Asked Questions about 37signals-review

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

FAQPage Schema
How do I review a Rails codebase for architectural drift and anti-patterns?

Run a structured Rails code review against modern patterns to identify architectural drift and anti-patterns. This detects CRUD philosophy violations, service-object misuse, and boolean flags, returning prioritized recommendations with severity, rationale, and actionable refactoring guidance.

What are 37signals Rails conventions for multi-tenancy and state records?

37signals Rails conventions favor state records over boolean flags and specific multi-tenant concern patterns. A structured code review identifies deviations from these patterns, offering concrete remediation steps and references to style-guide patterns to restore consistency and maintainability across the codebase.

How do I refactor Rails service objects to align with 37signals style?

Refactor Rails service objects by applying concrete recommendations generated from a structured code review. The review detects service-object anti-patterns and architectural drift, providing actionable refactors aligned with 37signals styles and escalating complex model logic to targeted pattern references.

Does this code review approach work for existing Rails refactors and architecture audits?

This code review approach works for existing Rails refactors, feature work, and architecture audits. It evaluates the codebase against a comprehensive checklist to ensure consistency, maintainability, and adherence to conventions, returning actionable feedback for safe implementation.

What is the best way to ensure consistency across a large Rails codebase?

The best way to ensure consistency across a Rails codebase is performing an architecture audit using a structured code review. This identifies deviations from established conventions and returns a prioritized list of improvements with concrete remediation references for models and concerns.