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.
98
99%
Does it follow best practices?
Impact
98%
1.38xAverage score across 26 eval scenarios
Passed
No known issues
A team maintains notifications_engine, a Rails engine gem used by several internal applications to handle in-app and email notifications. The engine is installed as a gem dependency across three production Rails apps. The team has accumulated a set of changes on the main branch since the last release (v1.2.1) and is ready to cut a new release.
The changes include: a new NotificationBatch model that allows sending grouped notifications in a single transaction, a fix for a bug where notification timestamps were stored in local time instead of UTC, and a configuration option allowing host apps to set a custom notification expiry period. There are no changes that break the existing public API.
Before publishing the gem, the team needs all the release preparation steps completed and the release artifacts ready to review. The gem should not be published until everything is in order.
Prepare the engine for release by completing all pre-publish steps. Update the necessary files in the engine directory, then produce a release summary saved as release-summary.md that the team lead can review before running the final publish command. The summary should include the recommended version number, reasoning for the bump level, and any open items or blockers.
The following files are provided as inputs. Extract them before beginning.
=============== FILE: lib/notifications_engine/version.rb =============== module NotificationsEngine VERSION = "1.2.1" end
=============== FILE: CHANGELOG.md ===============
Notification#mark_all_read! bulk methodnotifiable association=============== FILE: notifications_engine.gemspec =============== require_relative "lib/notifications_engine/version"
Gem::Specification.new do |spec| spec.name = "notifications_engine" spec.version = NotificationsEngine::VERSION spec.authors = ["Platform Team"] spec.email = ["platform@example.com"] spec.summary = "Rails engine for in-app and email notifications" spec.description = "Mountable Rails engine providing notification models, mailers, and delivery adapters" spec.homepage = "https://github.com/example/notifications_engine" spec.license = "MIT" spec.required_ruby_version = ">= 3.0"
spec.files = Dir["{app,config,db,lib}/**/*", "MIT-LICENSE", "Rakefile", "README.md"]
spec.add_dependency "rails", ">= 7.0" spec.add_development_dependency "rspec-rails" spec.add_development_dependency "factory_bot_rails" end
api-rest-collection
create-prd
ddd-boundaries-review
ddd-rails-modeling
ddd-ubiquitous-language
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
generate-tasks
mcp_server
rails-architecture-review
rails-background-jobs
rails-bug-triage
rails-code-conventions
rails-code-review
rails-engine-compatibility
rails-engine-docs
rails-engine-extraction
rails-engine-installers
rails-engine-release
rails-engine-reviewer
rails-engine-testing
rails-graphql-best-practices
rails-migration-safety
rails-review-response
rails-security-review
rails-skills-orchestrator
rails-stack-conventions
rails-tdd-slices
refactor-safely
rspec-best-practices
rspec-service-testing
ruby-service-objects
strategy-factory-null-calculator
ticket-planning
yard-documentation