MrCipherSmith Database Migration
Create, apply, and manage database migrations.
Arguments
/db-migrate create <name>— create new migration/db-migrate apply— apply pending migrations/db-migrate status— show migration status/db-migrate rollback— rollback last migration
Workflow
Step 1: Detect ORM/Migration Tool
Search for: prisma/schema.prisma, ormconfig.*, data-source.ts, knexfile.*, .sequelizerc, drizzle.config.ts, alembic.ini, migrations/ with raw SQL.
Step 2: Execute Command
Create:
| Tool | Command |
|---|---|
| Prisma | npx prisma migrate dev --name <name> |
| TypeORM | npx typeorm migration:generate -n <name> |
| Knex | npx knex migrate:make <name> |
| Sequelize | npx sequelize-cli migration:generate --name <name> |
| Drizzle | npx drizzle-kit generate:migration --name <name> |
| Alembic | alembic revision --autogenerate -m "<name>" |
Apply / Status / Rollback — analogous commands per tool.
Step 3: If Creating — Help Write Migration
- Ask what schema changes are needed (or infer from context)
- For schema-based ORMs — edit schema first, then generate
- For code-based migrations — generate template and fill in up/down
- Review generated migration before applying
Step 4: Apply & Verify
- Show migration SQL preview if possible
- Apply migration
- Verify with status command
Rules
- ALWAYS show migration content before applying in production
- ALWAYS confirm before rollback operations
- NEVER apply to production without explicit confirmation
- For destructive operations (drop table, remove column), double-warn
- If ORM can't be detected, ask the user