Skill: Create migration
SkillDatabases & dataCreate a new database migration following project naming and safety rules. Use when the user asks to add a migration or create a migration for a schema change.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Skill: Create migration skill
What this skill tells your AI
The instructions your AI receives, as published by girijashankarj/cursor-handbook in .cursor/skills/database/create-migration/SKILL.md and read by ahel’s review.
Trigger
When the user asks to add a migration, create a migration for a schema change, or "migrate the DB."
Steps
- Clarify — Confirm the change (new table, new column, index, constraint); ensure backward compatible where possible.
- Naming — Use format
YYYYMMDDHHMMSS_descriptive_action.sql(or project equivalent). - UP — Write the forward migration (ADD COLUMN with default, CREATE INDEX CONCURRENTLY where supported).
- DOWN — Write the rollback; test that DOWN reverts UP cleanly.
- Review — No raw DELETE; use soft delete if needed; parameterized only; add index for new FK/filters.
If a step fails
| Step | Failure | Recovery |
|---|---|---|
| Step 4 | DOWN does not revert UP cleanly | Fix DOWN to match UP; test both directions; document manual steps if schema change is irreversible |
| Step 5 | Review finds unsafe patterns | Rewrite migration; no raw DELETE; use soft delete; add defaults for new columns |
Rules
- Follow
.cursor/rules/database/migration-rules.mdcand schema-design rules. - Every table must have id, created_at, updated_at, and soft-delete column per project config.
Signals
- GitHub stars
- 30
- Forks
- 3
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
create-migration- Source
- github.com/girijashankarj/cursor-handbook