brokle-migration-workflow

Database migrations manage schema changes across PostgreSQL and ClickHouse. Use the migration CLI with `up` and `down` commands to create new migrations, apply them safely to development or production, and roll back if needed. The Skill provides SQL templates and step-by-step CLI workflows for both databases.

Design migrations separately for PostgreSQL (transactional) and ClickHouse (analytics). Use the migration CLI to create paired migrations with matching `up` and `down` SQL. The Skill provides schema templates, partitioning guidance, and safety checklists to ensure consistent deployment across both databases.

Seed files populate consistent test data in development, demo, and staging environments. Create seed files using the migration CLI, then run them alongside schema migrations. The Skill covers seed file creation, execution order, and environment-specific data setup.

Yes, dry-run previews show exactly what a migration will execute without committing changes. Use the migration CLI's dry-run feature to review SQL changes, check for conflicts, and validate safety before production deployment.

Rollback guards and health checks prevent data loss during reversions. The Skill provides dirtiness detection, status checks, and step-by-step rollback procedures. Always validate `down` migrations in staging before production use, and confirm database state before executing.

Yes, the CLI-driven workflow applies migrations across development, staging, and production with granular database selection and safety confirmations. Each environment uses the same migration files with environment-specific execution controls and status monitoring.