sandi-metz-reviewer

Identify Sandi Metz design violations in Ruby code and report structured feedback.

2|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/damacus/agent-skills --skill sandi-metz-reviewer-damacus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sandi-metz-reviewer
Source: https://github.com/damacus/agent-skills/tree/main/skills/sandi-metz-reviewer
Command: npx skills add https://github.com/damacus/agent-skills --skill sandi-metz-reviewer-damacus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams evaluate code quality against Sandi Metz's object-oriented design principles, enabling consistent feedback and guided refactoring.

Core Features & Use Cases

  • Enforces the four rules: class size, method length, parameter counts, and instance variable limits.
  • Evaluates adherence to SRP, Law of Demeter, and "Tell Don't Ask" patterns.
  • Generates actionable feedback with severity and suggested refactorings for Ruby projects.

Quick Start

Run the reviewer on a Ruby file and review the structured feedback it returns.

Frequently Asked Questions about sandi-metz-reviewer

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

FAQPage Schema
How do I check my Ruby code for Sandi Metz design violations?

To check Ruby code for Sandi Metz design violations, run the reviewer on a Ruby file to evaluate class and method sizes, parameter counts, instance variable limits, and Law of Demeter adherence. It returns structured feedback with severity levels and suggested refactorings aligned with POODR principles.

What are the four Sandi Metz rules for object-oriented design?

The four Sandi Metz rules for object-oriented design limit classes to 100 lines, methods to 5 lines, method parameters to 4, and instance variables per class to 4. This Skill enforces these rules alongside SRP and Law of Demeter checks to generate actionable refactoring guidance for Ruby projects.

How do I automate code review for Ruby refactoring based on SOLID principles?

Automate Ruby refactoring code review by applying this Skill to assess SOLID principles, specifically evaluating Single Responsibility and Tell Don't Ask patterns. It produces structured feedback with severity levels and actionable refactoring suggestions suitable for integration into developer workflows.

Does this code reviewer detect Law of Demeter violations in Ruby?

Yes, this code reviewer detects Law of Demeter violations in Ruby code. It evaluates dependency chains and object interaction patterns, reporting violations alongside SRP adherence and class size limits to provide structured, actionable refactoring feedback.

Can I integrate POODR principles into automated developer workflows?

Yes, you can integrate POODR principles into automated developer workflows. This Skill produces structured feedback aligned with Sandi Metz's object-oriented design rules, assessing dependencies and method sizes to enable consistent code quality evaluation during code review.

When should I use a POODR-based reviewer instead of general Ruby code analysis?

Use a POODR-based reviewer instead of general Ruby code analysis when you need to enforce specific object-oriented design constraints like the four rules, Single Responsibility Principle, and Law of Demeter. It provides targeted refactoring guidance for dependency management rather than basic syntax or style checks.