add-migration

To safely add a NOT NULL column to a populated table, you need a multi-phase rollout that applies a default value and backfills existing rows before enforcing the constraint. The skill classifies this as a mutating change and generates phased steps with verification checks to prevent locking or downtime.

Yes, this database migration approach works with Prisma, Drizzle, Knex, and raw SQL workflows. It detects your specific toolchain automatically and generates the correctly formatted migration files in the appropriate location for your framework.

The safest way to drop a column or change its type is a multi-phase deployment plan that classifies the action as destructive. This involves breaking the change into additive steps, verifying backfill operations, and dispatching a data-integrity review before final removal.

Adding a unique constraint safely requires checking for existing duplicate rows first, then applying the constraint in phases. The skill provides guardrails for unique constraints on existing duplicates and generates verification checks to ensure data integrity without causing deployment failures.

Adding an index can cause downtime because concurrent index creation locks the table in many database systems. The skill addresses unsafe index creation by classifying the schema change appropriately and generating a safe, phased rollout plan with necessary verification checks.