database-migration-helperlisted

# Database Migration Helper This skill helps you create database migration files that follow your project's ORM conventions and naming patterns. ## When to Use This Skill - User requests to create a database migration - Adding new tables or columns to the database - Modifying existing database schema - Creating indexes, constraints, or relationships - User mentions "migration", "schema change", or "database update" ## Instructions ### 1. Detect the ORM/Migration Tool First, identify which ORM or migration tool the project uses: - **Prisma**: Look for `prisma/schema.prisma` or `@prisma/client` in package.json - **Sequelize**: Look for `.sequelizerc` or `sequelize-cli` in package.json - **Knex**: Look for `knexfile.js` or `knex` in package.json - **TypeORM**: Look for `ormconfig.json` or `typeorm` in package.json - **Alembic** (Python): Look for `alembic.ini` or `alembic/` directory - **Django**: Look for `manage.py` and Django migrations in `*/migrations/` - **Active Record** (Rails): Look for `db/migrate/` directory - **Flyway**: Look for `flyway.conf` or `db/migration/` - **Liquibase**: Look for `liquibase.properties` or changelog files Use Glob to search for these indicator files. ### 2. Examine Existing Migrations Read existing migration files to understand: - Naming conventions (timestamp format, description format) - Directory structure - Migration file format (SQL, JavaScript, TypeScript, Python, etc.) - Coding patterns (up/down functions, forwards/rollback,