Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From migrate-tool
Generates a database migration file for schema changes, detecting the ORM or migration tool in use and producing reversible up/down migrations with optional data migration handling.
How this command is triggered — by the user, by Claude, or both
Slash command
/migrate-tool:db-migrateThe summary Claude sees in its command listing — used to decide when to auto-load this command
Generate a database migration file for schema changes. ## Steps 1. Detect the ORM or migration tool in use (Prisma, Drizzle, Knex, Alembic, Django, GORM). 2. Analyze the requested schema change: - Add/remove tables or columns. - Modify column types, constraints, or defaults. - Add/remove indexes or foreign keys. 3. Generate the migration file in the correct format for the tool. 4. Include both `up` and `down` migration functions for reversibility. 5. Handle data migrations if column types change: - Add new column, copy data, drop old column, rename new column. 6. Validate the ...
Generate a database migration file for schema changes.
up and down migration functions for reversibility.Migration: <YYYYMMDDHHMMSS>_<description>
Tool: <ORM/migration tool>
Up:
- <change description>
Down:
- <reverse change>
Data migration required: <yes/no>
2plugins reuse this command
First indexed Mar 30, 2026
npx claudepluginhub costrict-plugins-repo/github-trending-plan --plugin migrate-tool/db-migrateGenerates a database migration file for schema changes, detecting the ORM or migration tool in use and producing reversible up/down migrations with optional data migration handling.
/create-migrationGenerates a database migration file with both up and down logic, detecting the ORM or migration tool (Prisma, Knex, TypeORM, Alembic, Django, Rails) and producing properly named files with indexes, constraints, and data migration support.
/migration-genGenerates a database migration file from a schema change description or diff. Detects the target framework (Alembic, Flyway, Prisma, etc.) from project files and produces an up/down migration with idempotent guards, transaction boundaries, destructive-change warnings, and lock-risk annotations for large tables.
/migrationGenerates timestamped up/down migration files for PostgreSQL, MySQL, SQLite, MongoDB using SQL or ORM, with run instructions and testing guidance.
/migrateAuto-detects ORM/migration tool and generates idiomatic database migrations with backward compatibility checks, rollback validation, lock estimates. Applies, rolls back, or shows status via flags.
/fire-migrate-databaseGuides database migration between PostgreSQL, MySQL, SQLite, and SQL Server through a structured 6-step pipeline: assess, plan, execute, verify.