migrate

To safely add a NOT NULL database schema column, you need a migration workflow that assesses risk and plans data backfills. This Skill generates the migration steps, handles existing data constraints, and documents rollback procedures to prevent data loss.

Yes, you can generate database migrations using Prisma, as well as Drizzle, Knex, and TypeORM. The Skill provides ORM-aware migration file generation, allowing you to review the underlying SQL before applying schema changes to your database.

The safest way to plan a database schema rollback is to use a migration workflow that classifies operational risk and documents rollback steps. This Skill generates rollback procedures for adding indexes or creating tables to ensure safe schema reversal.

Handling production database schema changes and data backfills requires a structured migration process with risk assessment. This Skill manages the workflow by generating reviewable SQL, planning backfill steps, and outlining a clear rollback strategy.

Yes, this database migration workflow includes risk assessment for schema changes. It classifies the risk level of operations like adding or removing columns and provides a clear execution plan with documented rollback steps before applying changes.