generate-migration
Generate Django database migrations for Sentry. Use when creating migrations, adding/removing columns or tables, adding indexes, or resolving migration conflicts.
80
100%
Does it follow best practices?
Impact
—
No eval scenarios have been run
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 communicates its purpose, scope, and trigger conditions. It uses third person voice, lists specific concrete actions, includes natural trigger terms developers would use, and has an explicit 'Use when' clause. The Sentry-specific scoping makes it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: generating Django database migrations, creating migrations, adding/removing columns or tables, adding indexes, and resolving migration conflicts. | 3 / 3 |
Completeness | Clearly answers both 'what' (generate Django database migrations for Sentry) and 'when' (explicit 'Use when' clause covering creating migrations, adding/removing columns or tables, adding indexes, resolving migration conflicts). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Django', 'migrations', 'columns', 'tables', 'indexes', 'migration conflicts', 'Sentry'. These are terms developers naturally use when working with database schema changes. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the combination of 'Django', 'Sentry', and 'database migrations' — this is a clear niche that is unlikely to conflict with other skills. The Sentry-specific scoping further reduces overlap risk. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that provides Sentry-specific Django migration guidance with high actionability and clear multi-step workflows. It is concise, assumes Claude's competence with Django fundamentals, and focuses exclusively on the non-obvious Sentry-specific patterns (SafeDeleteModel, db_default, historical_silo_assignments, two-phase deletions). The validation steps (sqlmigrate, migrate with safety checks) and deploy gates between phases demonstrate strong workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude knows Django, migrations, and Python. Every section provides only the specific Sentry-relevant details (e.g., `db_default` instead of `default`, `SafeDeleteModel`, `historical_silo_assignments`) without explaining basic concepts. | 3 / 3 |
Actionability | Provides concrete, executable commands (`sentry django makemigrations`, `bin/update-migration`), specific class/method names (`SafeRemoveField`, `DeletionAction.MOVE_TO_PENDING`), exact file paths (`src/sentry/db/router.py`), and copy-paste ready bash commands. Every guideline is specific and directly usable. | 3 / 3 |
Workflow Clarity | Multi-step processes (deleting columns, removing models) are clearly sequenced with numbered steps and explicit deploy checkpoints between phases. The 'After Generating' section includes a validation step (`sqlmigrate` to verify SQL, `migrate` to trigger safety checks). The two-phase model removal process has clear phase boundaries with deploy gates. | 3 / 3 |
Progressive Disclosure | For a skill with no bundle files, the content is well-organized with clear section headers (Commands, After Generating, Guidelines with subsections). The length is appropriate — not monolithic — and each section is focused. No external references are needed given the scope, and the structure supports quick scanning. | 3 / 3 |
Total | 12 / 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
- getsentry/sentry
- Commit
552fb5c
- 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.