solid-principles

To identify SOLID principle violations in Ruby code, apply detection heuristics and violation patterns for Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion. This Skill provides specific checklists to quickly spot design flaws during code reviews.

The best way to refactor a Ruby class violating the Single Responsibility Principle is to apply Ruby-idiomatic refactoring strategies. This involves splitting the class into distinct objects based on detected violation patterns to improve overall maintainability and flexibility.

Yes, you can use SOLID design principles to review an existing Ruby pull request. This Skill offers actionable checklists and heuristics to evaluate code design, detect Open/Closed violations, and suggest Ruby-idiomatic refactoring strategies before merging.

You need to apply the Liskov Substitution Principle in Ruby when designing class hierarchies where subclasses must be substitutable for their base classes without altering program correctness. Use this Skill to detect violation patterns and implement proper interface segregation.

Dependency Inversion in Ruby-idiomatic code design involves depending on abstractions rather than concrete implementations. This Skill provides detection heuristics and refactoring strategies to properly invert dependencies, ensuring your Ruby code remains flexible and maintainable.