c3f43d8b61
- Add 60 new agents across all 10 categories (75 -> 135) - Add 95 new plugins with command files (25 -> 120) - Update all agents to use model: opus - Update README with complete plugin/agent tables - Update marketplace.json with all 120 plugins
1.2 KiB
1.2 KiB
Generate a database migration file for schema changes.
Steps
- Detect the ORM or migration tool in use (Prisma, Drizzle, Knex, Alembic, Django, GORM).
- Analyze the requested schema change:
- Add/remove tables or columns.
- Modify column types, constraints, or defaults.
- Add/remove indexes or foreign keys.
- Generate the migration file in the correct format for the tool.
- Include both
upanddownmigration functions for reversibility. - Handle data migrations if column types change:
- Add new column, copy data, drop old column, rename new column.
- Validate the migration against the current schema state.
- Run the migration in dry-run mode if the tool supports it.
Format
Migration: <YYYYMMDDHHMMSS>_<description>
Tool: <ORM/migration tool>
Up:
- <change description>
Down:
- <reverse change>
Data migration required: <yes/no>
Rules
- Every migration must be reversible with a down function.
- Never drop columns or tables without a data backup step.
- Use transactions for multi-step migrations when supported.
- Test migrations against a copy of production data structure.
- Name migrations with timestamps to prevent ordering conflicts.