CtrlK
BlogDocsLog inGet started
Tessl Logo

igmarin/rails-agent-skills

Curated library of AI agent skills for Ruby on Rails development. Covers code review, architecture, security, testing (RSpec), engines, service objects, DDD patterns, and workflow automation.

95

2.21x
Quality

97%

Does it follow best practices?

Impact

91%

2.21x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

SKILL.mdrails-engine-release/

name:
rails-engine-release
description:
Use when preparing a Rails engine gem release. Generates CHANGELOG.md entries, produces step-by-step upgrade notes, sets semantic version constants, updates gemspec metadata, and sequences gem build and publish commands. Trigger words: version bump, changelog, deprecation, gemspec, upgrade, migration guide, release, publish gem, ship gem.

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.

Quick Reference

Release StepAction
Version bumpPatch (bug fixes), Minor (new features), Major (breaking changes); update version constant once
ChangelogDocument user-visible changes, not commits; group by Added/Changed/Fixed/Deprecated
DeprecationsDocument removal plan and replacement; keep deprecated code for at least one minor cycle
GemspecVerify metadata, dependencies, and tested Rails/Ruby versions match constraints

HARD-GATE

DO NOT release without updating CHANGELOG and version file.

Release Order

  1. Confirm scope and compatibility impact — is this patch, minor, or major?
  2. Run full test suite: bundle exec rspec. Fix all failures before proceeding.
  3. Set the version bump — update the version constant once: module MyEngine; VERSION = "1.2.0"; end in lib/my_engine/version.rb.
  4. Update changelog and upgrade notes.
  5. Verify gemspec metadata and dependencies match tested Rails/Ruby versions.
  6. Dry-run the gem build: gem build *.gemspec && gem push --dry-run *.gem. Verify contents.
  7. Confirm installation docs and README match the release — update if needed.
  8. Publish: gem push *.gem.

Versioning Rules

  • Patch: bug fixes and internal changes without public behavior breakage.
  • Minor: backward-compatible features and new extension points.
  • Major: breaking changes to API, setup, routes, migrations, configuration, or supported framework versions.

If the engine requires host changes during upgrade, document them explicitly even if the version bump is minor.

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 EXAMPLES.md for a full changelog entry and upgrade note template.

Output Style

When asked to prepare a release:

  1. Recommend the version bump and why.
  2. Draft concise changelog entries.
  3. Draft upgrade notes for host apps.
  4. Call out any release blockers clearly.

Integration

SkillWhen to chain
rails-engine-docsWhen updating README, setup instructions, or API docs for the release
rails-engine-compatibilityWhen verifying Rails/Ruby version support or deprecation impact
rails-engine-testingWhen ensuring tests pass before release and match documented behavior

rails-engine-release

EXAMPLES.md

SKILL.md

README.md

tile.json