igmarin/ruby-core-skills
Curated library of 16 public Ruby AI agent skills: 10 atomic skills (YARD docs, service objects, calculator pattern, API clients, DDD, bug triage, code review, skill routing), 5 process-discipline skills (TDD, refactoring, review, security, test planning), and 1 planning skill (TDD task generation). Zero agents — this is a foundational library consumed by framework-specific tiles like rails-agent-skills and hanakai-yaku.
95
96%
Does it follow best practices?
Impact
95%
1.05xAverage score across 16 eval scenarios
Passed
No known issues
BOUNDARY_GUIDE.mdskills/testing/triage-bug/
Bug Triage Boundary Guide
Maps common bug shapes to the highest-value first failing test.
| Bug shape | Likely first test | Path example |
|---|---|---|
| Wrong status code, params handling, response payload | Request or integration test | spec/requests/ or test/integration/ |
| Invalid state transition, validation, calculation | Unit or service test | spec/models/ or test/unit/ |
| Async side effect missing or duplicated | Worker/job or unit test | spec/workers/ or test/jobs/ |
| Component integration/configuration regression | Integration test | Component test suite path |
| Third-party mapping/parsing issue | Integration or client-layer test | spec/services/module_name/ |
Diagnosing the Right Layer
- HTTP/API symptoms (wrong status, wrong payload shape, redirect loops): start at request or integration level
- Data symptoms (wrong value saved, wrong validation message): start at unit or service class level
- Timing/Async symptoms (missing notification, job not enqueued): start at background worker or unit service level
- Integration/Component symptoms (module loading errors, route not found): use integration test or dummy app integration test
When the Boundary Is Unclear
- Write the test at the highest visible symptom boundary first.
- Run it — if it fails for the wrong reason (e.g., test setup error), move down a layer.
- The correct boundary is where the failure message directly names the missing behavior.
docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
skills
code-quality
respond-to-review
ddd
define-domain-language
model-domain
review-domain-boundaries
docs
write-yard-docs
orchestration
skill-router
patterns
create-service-object
implement-calculator-pattern
planning
generate-tdd-tasks
process
testing
triage-bug