Curated library of 42 public AI agent skills for Ruby on Rails development, plus 5 callable workflow skills. Organized by category: planning, testing, code-quality, ddd, engines, infrastructure, api, patterns, context, orchestration, and workflows. Covers code review, architecture, security, testing (RSpec), engines, service objects, DDD patterns, and TDD automation.
97
97%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Use this skill when the task is to ship a Rails engine as a gem or prepare a new version.
DO NOT release without updating CHANGELOG and version file.
| Bump | When to use | Action |
|---|---|---|
| Patch | Bug fixes and internal changes without public behavior breakage | Update version constant, document under Fixed |
| Minor | Backward-compatible features and new extension points | Update version constant, document under Added/Changed |
| Major | Breaking changes to API, setup, routes, migrations, config, or supported framework versions | Update version constant, document under Changed/Deprecated; write explicit upgrade notes |
If the engine requires host changes during upgrade, document them explicitly even if the version bump is minor.
bundle exec rspec. Fix all failures before proceeding.module MyEngine; VERSION = "1.2.0"; end in lib/my_engine/version.rb.gem build *.gemspec && gem push --dry-run *.gem. Verify contents.gem push *.gem.## [1.2.0] - 2024-03-15
### Added
- `widget_count` config option to limit dashboard widgets (default: 10).
### Changed
- Minimum Rails version is now 7.0.See assets/examples.md for a full changelog entry and upgrade note template.
Load these files only when their specific content is needed:
When asked to prepare a release, produce a release summary ready for team lead review, with code blocks for all file changes. Required deliverables:
lib/<engine>/version.rbbundle exec rspec| Skill | When to chain |
|---|---|
| rails-engine-docs | When updating README, setup instructions, or API docs for the release |
| rails-engine-compatibility | When verifying Rails/Ruby version support or deprecation impact |
| rails-engine-testing | When ensuring tests pass before release and match documented behavior |
build
docs
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
workflows