rails-migration-safety
Use when planning or reviewing production database migrations, adding columns, indexes, constraints, backfills, renames, table rewrites, or concurrent operations. Covers phased rollouts, lock behavior, rollback strategy, strong_migrations compliance, and deployment ordering for schema changes.
95
96%
Does it follow best practices?
Impact
91%
1.49xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its scope around production database migrations with specific, concrete actions and explicit trigger guidance. It uses third person voice appropriately and includes a rich set of natural trigger terms that developers would use. The description is concise yet comprehensive, covering both the 'what' and 'when' effectively.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'adding columns, indexes, constraints, backfills, renames, table rewrites, concurrent operations' and covers specific concerns like 'phased rollouts, lock behavior, rollback strategy, strong_migrations compliance, deployment ordering.' | 3 / 3 |
Completeness | Explicitly answers both what ('planning or reviewing production database migrations, adding columns, indexes...') and when ('Use when planning or reviewing production database migrations...'). The 'Use when' clause is present and clearly defines trigger conditions. | 3 / 3 |
Trigger Term Quality | Includes many natural keywords a user would say: 'database migrations', 'adding columns', 'indexes', 'constraints', 'backfills', 'renames', 'table rewrites', 'concurrent operations', 'rollback strategy', 'strong_migrations', 'schema changes'. These cover a wide range of terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to production database migrations and schema changes with specific triggers like 'strong_migrations compliance', 'lock behavior', and 'deployment ordering' that distinguish it from general database or code skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that is concise, actionable, and well-structured for production database migration safety. It excels at providing concrete code examples alongside clear risk explanations and phased rollout workflows. The only minor weakness is that all content is inline rather than using progressive disclosure to separate the quick reference from deeper pattern documentation, though for its current length this is a minor concern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It uses tables for quick reference, avoids explaining what Rails migrations are or how databases work, and every section adds actionable value. No unnecessary preamble or concept explanations. | 3 / 3 |
Actionability | Provides executable Ruby code examples for both risky and safe patterns, specific method calls (algorithm: :concurrent, disable_ddl_transaction!, change_column_null), and a clear quick-reference table mapping operations to concrete safe patterns. | 3 / 3 |
Workflow Clarity | The Review Order section provides a clear 5-step sequence. The safe pattern example explicitly shows a 3-step phased deployment with validation gates (backfill must complete before adding NOT NULL). The HARD-GATE section serves as explicit validation checkpoints, and the Red Flags section provides a verification checklist. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and tables, but it's entirely self-contained with no references to external files for deeper topics. The Integration table references other skills but doesn't link to supplementary materials for advanced scenarios like complex type changes or multi-database setups that could benefit from separate documents. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- igmarin/rails-agent-skills
- Commit
ae8ea63
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.