Migrate Plan
/migrate-planAudit a Postgres schema change before writing it. Catches the lock risks that turn 30-second deploys into 10-minute outages.
Install in one command
mkdir -p ~/.claude/skills/migrate-plan && curl -fsSL https://eliteaiadvantage.com/skills/migrate-plan/SKILL.md -o ~/.claude/skills/migrate-plan/SKILL.mdThen run /migrate-plan in Claude Code.
What it is
Migrations on a live Postgres database carry asymmetric risk: a careful one ships in 30 seconds, a careless one locks a table for 10 minutes during peak traffic and you're explaining downtime to users. Migrate Plan audits the change before you write it. Ship Check audits after. Both matter; this is the upstream half.
Works for Prisma and Drizzle alike, the risks are at the SQL layer, not the ORM. Identifies the change type, names the lock risks, proposes a safe staged pattern when needed, drafts the migration, and lists the pre-flight checks.
Why it's useful
- →Categorizes the change type with a risk score, NOT NULL on big tables is 🔴, nullable column is 🟢.
- →Proposes staged patterns for risky changes (add nullable → backfill → set NOT NULL) instead of one-shot DDL.
- →Flags the Prisma rename gotcha (where Prisma writes DROP+ADD instead of RENAME).
- →Includes a pre-flight checklist that pairs with /ship-check before the actual deploy.
- →Calibrated for Railway Postgres realities, connection limits, maintenance windows, replication.
When to use it
- •About to author a Prisma or Drizzle schema change.
- •Adding a NOT NULL column to a table you're not 100% sure is small.
- •Adding a unique constraint to a table that may have duplicates.
- •Any migration that scared you a little when you typed it.
How it helps with Claude
Without this skill, "should this migration be safe?" is a hand-wave. Migrate Plan reads the schema, categorizes the change, names the specific risk, proposes the staged pattern if needed, and drafts the SQL. Claude stops saying "should be fine" and starts giving evidence-grounded plans with rollback paths.