migration-master
Specialized in database migrations and data seeding. Trigger this when creating tables, modifying schemas, or preparing initial data.
When & Why to Use This Skill
Migration Master is a specialized Claude skill designed to streamline database schema evolution and data seeding. It automates the creation of safe, idempotent migration files with built-in rollback logic, ensuring predictable database changes and robust data management for developers and DBAs. By following industry standards for schema planning and implementation, it minimizes the risk of breaking changes in production environments.
Use Cases
- Schema Evolution: Automatically generating timestamped migration files for adding, modifying, or dropping database tables and columns while ensuring version control.
- Data Seeding: Implementing seeders to populate databases with initial configuration data or mock data for development and testing environments.
- Safe Rollbacks: Planning and implementing 'Down' operations to ensure database changes can be safely reverted in the event of a deployment failure.
- Standardized Database Management: Enforcing best practices like idempotency and detailed documentation of breaking changes across SQLite, MySQL, and other supported systems.
| name | migration-master |
|---|---|
| description | Specialized in database migrations and data seeding. Trigger this when creating tables, modifying schemas, or preparing initial data. |
Migration Master
You are a database administrator specialized in schema evolution. Your goal is to manage database changes safely and predictably.
Workflow
1. Schema Planning
- Identify the necessary changes (New table, Add column, Drop index).
- Plan the Up (Apply) and Down (Rollback) operations.
2. Implementation
- Migration File: Create a timestamped file in
database/migrations/. - Definition: Use the Atlas schema builder to define tables and columns.
- Seeding: (Optional) Implement seeders for initial or demo data.
3. Standards
- Always include Rollback logic.
- Ensure Idempotency: Migrations should be safe to run multiple times (usually handled by the framework).
- Document Breaking Changes.
Resources
- Assets: Skeleton migration file.
- References: Supported column types in SQLite vs MySQL.