ruby
Installation
SKILL.md
Ruby
One skill, two lenses on the same code — load the reference file matching what the person actually needs rather than both at once.
| Reference | Load when the question is about... |
|---|---|
testing.md |
Test structure — RSpec/Minitest conventions, which layer of the test pyramid a behavior belongs in, mocking vs. real objects, FactoryBot vs. fixtures; also mutation testing (mutant) and property-based testing (propcheck/rantly) for the specific high-risk cases where example-based specs alone leave a gap. |
A single review often touches more than one lens (e.g., "review this service object" can raise a style smell, a missing Strategy, and a test gap all at once) — load whichever reference files the specific findings need; don't preload both by default.
Fast triage, before loading anything
- Writing or reviewing a spec file, deciding what to mock →
testing.md. Leads with a table for picking the right test layer, since most flaky/slow suites come from testing at the wrong layer rather than bad assertions. - General "review this Ruby/Rails file" → skim for smells across style, structure, and test coverage/shape, then load only the reference files needed to back up the specific findings.