igmarin/rails-agent-skills
Curated library of 39 AI agent skills for Ruby on Rails development. Organized by category: planning, testing, code-quality, ddd, engines, infrastructure, api, patterns, context, orchestration, and workflows. Includes 5 callable workflow skills (rails-tdd-loop, rails-review-flow, rails-setup-flow, rails-quality-flow, rails-engines-flow) for complete development cycles. Covers code review, architecture, security, testing (RSpec), engines, service objects, DDD patterns, and TDD automation.
95
98%
Does it follow best practices?
Impact
95%
1.20xAverage score across 35 eval scenarios
Passed
No known issues
HEURISTICS.mdskills/code-quality/refactor-safely/
Refactor Safety Heuristics
Use this file as a review checklist during structural changes.
Common Mistakes
| Mistake | Reality |
|---|---|
| "Quick refactor, no tests needed" | No characterization tests means no safety net. |
| Mixing behavior change with structural change | Mixed intent is hard to validate and review. |
| Renaming many call sites in one commit | Do small batches with tests between batches. |
| Adding abstractions just to match a pattern | Abstractions must serve a real boundary. |
| Deleting old path before proving new path | Keep temporary compatibility until migration is complete. |
Red Flags
- Plan touches many unrelated call sites at once.
- No tests prove current behavior before starting.
- Structural cleanup is mixed with new feature work.
- Old and new paths diverge without migration plan.
- New abstractions exist only for pattern purity.
- More than 3 refactor steps without running tests.
- Language like "should", "probably", "seems to" when claiming test success.
Review Prompts
- What behavior is explicitly declared as stable?
- Which exact tests protect each refactor step?
- What temporary compatibility code exists, and when will it be removed?
- What is the smallest next reversible step?
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
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
scenario-29
scenario-30
scenario-31
scenario-32
scenario-33
scenario-34
scenario-35
mcp_server
skills
api
api-rest-collection
rails-graphql-best-practices
code-quality
rails-architecture-review
rails-code-conventions
rails-code-review
rails-review-response
rails-security-review
rails-stack-conventions
assets
snippets
refactor-safely
context
rails-context-engineering
rails-project-onboarding
ddd
ddd-boundaries-review
ddd-rails-modeling
ddd-ubiquitous-language
engines
rails-engine-compatibility
rails-engine-docs
rails-engine-extraction
rails-engine-installers
rails-engine-release
rails-engine-reviewer
rails-engine-testing
infrastructure
rails-api-versioning
rails-background-jobs
rails-database-seeding
rails-frontend-hotwire
rails-migration-safety
rails-performance-optimization
orchestration
rails-skills-orchestrator
patterns
ruby-service-objects
strategy-factory-null-calculator
yard-documentation
planning
create-prd
generate-tasks
ticket-planning
testing
rails-bug-triage
rails-tdd-slices
rspec-best-practices
rspec-service-testing