Agent skill · software engineering · aiskillstore
database-migration
Execute database migrations across ORMs and platforms with zero-downtime strategies, data transformation, and rollback procedures. Use when migrating databases, changing schemas, performing data transformations, or implementing zero-downtime deployment strategies.
Why this skill is useful
Adds executable migration scripts for multiple ORMs that facilitate zero-downtime deployments and complex schema transformations.
What it needs
Requires prisma, sequelize-cli, typeorm installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Database Migration Master database schema and data migrations across ORMs (Sequelize, TypeORM, Prisma), including rollback strategies and zero-downtime deployments. When to Use This Skill Migrating between different ORMs Performing schema transformations Moving data between databases Implementing rollback procedures Zero-downtime deployments Database version upgrades Data model refactoring ORM Migrations Sequelize Migrations TypeORM Migrations Prisma Migrations Schema Transformations Adding Columns with Defaults Renaming Columns (Zero Downtime) Changing Column Types Data Transformations Complex Data Migration Rollback Strategies Transaction-Based Migrations Checkpoint-Based Rollback Zero-Downtime Migrations Blue-Green Deployment Strategy Cross-Database Migrations PostgreSQL to MySQL Resources references/orm-switching.md: ORM migration guides references/schema-migration.md: Schema transformation patterns references/data-transformation.md: Data migration scripts references/rollback-strategies.md: Rollback procedures assets/schema-migration-template.sql: SQL migration templates assets/data-migration-script.py: Data migration utilities scripts/test-migration.sh: Migration testing script Best Practices 1. Always Provide Rollback: Every up() needs a down() 2. Test Migrations: Test on staging first 3. Use Transactions: Atomic migrations when possible 4. Backup First: Always backup before migration 5. Small Changes: Break into small, incremental steps 6. Monitor: Watch for errors during deployment 7. Document: Explain why and how 8. Idempotent: Migrations should be rerunnable Common Pitfalls Not testing rollback procedures Making breaking changes without downtime strategy Forgetting to handle NULL values Not considering index performance Ignoring foreign key constraints Migrating too much data at once
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/database-migration--34fc76