How does the skill handle 'Shameless Green'?

It encourages writing the simplest possible solution first and waiting for duplication to appear before abstracting, following the '99 Bottles of OOP' philosophy.

Does this skill only work for Ruby code?

While the skill is optimized for Ruby and Rails based on Sandi Metz's books, the object-oriented design principles it enforces are applicable to most OO languages.

What are Sandi Metz's 'Four Rules'?

The rules specify a maximum of 100 lines per class, 5 lines per method, 4 parameters per method, and 4 instance variables per class.

Can it help fix Law of Demeter violations?

Yes, it identifies long message chains and suggests delegation or moving behavior to the object that owns the data to ensure objects only talk to their 'immediate friends.'

Sandi Metz OO Design Reviewer

Name: Sandi Metz OO Design Reviewer
Author: el-feo

byel-feo

협업 도구

Analyzes code using Sandi Metz's object-oriented design principles to ensure maintainable, flexible, and cleanly structured Ruby applications.

소개

This skill transforms Claude into an expert code reviewer specializing in the principles established by Sandi Metz in 'Practical Object-Oriented Design in Ruby' and '99 Bottles of OOP.' It automatically evaluates code against the 'Four Rules' (measuring class/method length and complexity), checks for Single Responsibility violations, identifies Law of Demeter issues, and suggests refactoring patterns like replacing conditionals with polymorphism. It is an essential tool for Ruby and Rails developers looking to reduce technical debt, improve architectural quality, and follow the 'Shameless Green' philosophy for incremental software improvement.

주요 기능

Automated 'Four Rules' check for class/method size and parameter counts
0 GitHub stars
Guidance on replacing complex conditionals with polymorphic behavior
Actionable refactoring suggestions based on the 'Flocking Rules' approach
Detection of Law of Demeter and 'Tell, Don't Ask' violations
Identification of Single Responsibility Principle (SRP) code smells

사용 사례

Mentoring developers on foundational object-oriented design principles through live feedback
Identifying hidden coupling and 'feature envy' in complex legacy codebases
Conducting automated code reviews during the refactoring phase of a Ruby on Rails project

소개

주요 기능

Automated 'Four Rules' check for class/method size and parameter counts
0 GitHub stars
Guidance on replacing complex conditionals with polymorphic behavior
Actionable refactoring suggestions based on the 'Flocking Rules' approach
Detection of Law of Demeter and 'Tell, Don't Ask' violations
Identification of Single Responsibility Principle (SRP) code smells

사용 사례

Mentoring developers on foundational object-oriented design principles through live feedback
Identifying hidden coupling and 'feature envy' in complex legacy codebases
Conducting automated code reviews during the refactoring phase of a Ruby on Rails project