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
SKILL.mdskills/engines/rails-engine-release/
- name:
- rails-engine-release
- license:
- MIT
- description:
- Use when preparing a Rails engine gem release. Generates CHANGELOG.md entries, produces step-by-step upgrade notes for host apps, sets semantic version constants, verifies gemspec metadata, confirms test suite passes, and sequences gem build and publish commands. Trigger words: version bump, changelog, deprecation, gemspec, upgrade, migration guide, release, publish gem, ship gem, verify gemspec, test suite.
Rails Engine Release
Use this skill when the task is to ship a Rails engine as a gem or prepare a new version.
Release work should make upgrades predictable for host applications.
HARD-GATE
DO NOT release without updating CHANGELOG and version file.
Versioning & Quick Reference
| 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.
Release Order
- Confirm scope and compatibility impact — is this patch, minor, or major?
- Run full test suite:
bundle exec rspec. Fix all failures before proceeding. - Set the version bump — update the version constant once:
module MyEngine; VERSION = "1.2.0"; endinlib/my_engine/version.rb. - Update changelog and upgrade notes.
- Verify gemspec metadata and dependencies match tested Rails/Ruby versions.
- Dry-run the gem build:
gem build *.gemspec && gem push --dry-run *.gem. Verify contents. - Confirm installation docs and README match the release — update if needed.
- Publish:
gem push *.gem.
Changelog Guidelines
- Document user-visible changes, not commits; group by Added/Changed/Fixed/Deprecated.
- For deprecations, document removal plan and replacement; keep deprecated code for at least one minor cycle.
Examples
## [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.
Extended Resources (Progressive Disclosure)
Load these files only when their specific content is needed:
- assets/release_checklist.md — Use when you need a detailed step-by-step verification checklist before finalizing the release
- assets/release_notes_template.md — Use when drafting GitHub release notes or long-form release announcements
- assets/examples.md — Reference for full changelog entries and upgrade note templates
Output Style
When asked to prepare a release, produce a release summary ready for team lead review, with code blocks for all file changes. It MUST include:
- Version bump recommendation — New version (patch/minor/major) with explicit reasoning
- Version constant — Updated
lib/<engine>/version.rbwith the newVERSION = "x.y.z" - CHANGELOG entries — User-facing changes under Added/Changed/Fixed/Deprecated headers
- Upgrade notes — Steps host apps must take (config changes, migration steps, dependency updates)
- Gemspec verification — Confirm metadata, files, and dependencies match tested Rails/Ruby versions
- Test suite status — Confirm
bundle exec rspecpasses before proceeding to build - Release blockers — Open issues preventing release, or explicitly state "No blockers"
Integration
| 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 |
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