database-migration-helper

Database migrations with rollback support require explicit up and down operations, handling index management and data transformations within the same migration flow to ensure safe schema changes. This skill generates those reversible migration patterns automatically.

The safest way to add a column and backfill rows is using a structured migration that applies schema changes and corresponding data transformations sequentially, while guaranteeing a reversible rollback path. This ensures clean reversion if the deployment fails.

Yes, you can generate reversible schema changes for Prisma, TypeORM, Alembic, Sequelize, and raw SQL workflows. The generated templates include provider-specific guidance for index management, default handling, and explicit data-migration steps.

Database migration down operations handle data transformations by defining explicit reverse data-migration steps alongside schema reversion. This guarantees that backfilled or converted column values are safely rolled back to their original state.

ORM templates for complex schema evolution require well-defined up and down operations, explicit index management, and default handling tailored to the target SQL dialect. Raw SQL workflows may be necessary when provider-specific ORM templates lack advanced data transformation capabilities.