Creates Rails concerns for shared behavior across models or controllers with TDD. Use when extracting shared code, creating reusable modules, DRYing up models/controllers, or when user mentions concerns, modules, mixins, or shared behavior.
91
88%
Does it follow best practices?
Impact
96%
1.05xAverage score across 3 eval scenarios
Passed
No known issues
Model concern TDD workflow
Spec file created first
100%
100%
Spec uses test class pattern
50%
50%
Concern file location
100%
100%
ActiveSupport::Concern usage
100%
100%
included block for callbacks/validations
100%
100%
Instance methods placement
100%
100%
Single responsibility
100%
100%
Descriptive module name
100%
100%
RED step documented
57%
71%
GREEN step documented
57%
71%
Concern structure and placement
Concern file location
100%
100%
ActiveSupport::Concern
100%
100%
included block for scopes
100%
100%
included block for callbacks
100%
100%
class_methods block used
100%
100%
Instance methods placement
100%
100%
Single responsibility
100%
100%
Descriptive module name
100%
100%
Spec file location
100%
100%
Spec tests via including model
100%
100%
Model includes concern
100%
100%
Controller concern with request specs
Controller concern location
100%
100%
ActiveSupport::Concern
100%
100%
included block for before_action
100%
100%
class_methods block used
0%
100%
Instance methods placement
100%
100%
Request spec location
100%
100%
Request spec type
100%
100%
Single responsibility
100%
100%
Descriptive module name
100%
100%
Controller includes concern
100%
100%
15fdeaf
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.