Guides Test-Driven Development workflow with Red-Green-Refactor cycle. Use when the user wants to implement a feature using TDD, write tests first, follow test-driven practices, or mentions red-green-refactor.
89
87%
Does it follow best practices?
Impact
93%
1.72xAverage score across 3 eval scenarios
Passed
No known issues
Service object TDD workflow
Frozen string literal
0%
100%
Rails helper require
0%
100%
Correct spec location
100%
100%
RSpec.describe with type
0%
100%
subject using described_class
0%
100%
context blocks present
100%
100%
One behavior per it block
0%
100%
Service call pattern
28%
42%
RED phase documented
100%
100%
GREEN phase minimal
77%
77%
REFACTOR phase documented
100%
100%
build over create preference
100%
100%
No anti-patterns
100%
100%
Model spec patterns and test types
Frozen string literal
0%
100%
Rails helper require
100%
100%
Correct file location
100%
100%
RSpec.describe with type
100%
100%
Validation matchers
0%
100%
Association matchers
0%
100%
Dependent destroy association
0%
100%
Scope test uses let!
0%
100%
contain_exactly for scope
100%
100%
One behavior per it
0%
100%
build over create
50%
100%
No mystery guests
90%
100%
Request spec and TDD refactoring
Frozen string literal
0%
100%
Rails helper require
100%
100%
Correct spec location
100%
100%
RSpec.describe with request type
100%
100%
context blocks for scenarios
57%
100%
One behavior per it
14%
14%
format documentation flag
0%
100%
RED phase documented
100%
100%
GREEN phase minimal
100%
100%
One change at a time
20%
30%
Specs re-run per change
50%
100%
No brittle error messages
100%
100%
Implementation not spec fixed
100%
100%
15fdeaf
Table of Contents
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.