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
{
"context": "Tests whether the agent follows the rails-engine-release skill when preparing a Rails engine gem for release: updating CHANGELOG and version constant before anything else, applying semantic versioning correctly, following the release order, and producing all required output artifacts.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Version constant updated",
"description": "The version file (lib/<engine>/version.rb or equivalent) has its VERSION constant updated to the new version number",
"max_score": 10
},
{
"name": "CHANGELOG updated",
"description": "The CHANGELOG.md file is updated with entries for the new release (new version header and list of changes)",
"max_score": 12
},
{
"name": "Upgrade notes produced",
"description": "Upgrade notes are drafted — either as a separate file or as a section in the output — describing what consumers need to do when upgrading",
"max_score": 10
},
{
"name": "Semantic version bump correct",
"description": "The version bump type (patch/minor/major) matches the nature of the changes: patch for bug fixes only, minor for new backward-compatible features, major for breaking changes",
"max_score": 12
},
{
"name": "Version bump reasoning provided",
"description": "The output explicitly states WHY this version bump level was chosen (e.g. 'minor because new feature X was added without breaking the existing API')",
"max_score": 10
},
{
"name": "Gemspec verified",
"description": "The agent checks or mentions verifying gemspec metadata (authors, description, files, dependencies) as part of the release process",
"max_score": 8
},
{
"name": "Test suite mentioned",
"description": "The agent mentions running or confirms that the full test suite passes as a step in the release process",
"max_score": 8
},
{
"name": "Blockers called out",
"description": "The output explicitly calls out any blockers or open items that would prevent a clean release (or states there are none)",
"max_score": 8
},
{
"name": "CHANGELOG entries are specific",
"description": "The CHANGELOG entries describe specific changes (feature names, bug descriptions) rather than generic placeholder text like 'various improvements'",
"max_score": 10
},
{
"name": "No release without CHANGELOG",
"description": "The agent does NOT proceed to gem build or publish steps until both the CHANGELOG and version file have been updated",
"max_score": 12
}
]
}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