alexzhu0 Database Migration Risk Review
Purpose
Find practical risks in database migrations before they reach production.
Fit
- Use when schema, data, index, or backfill changes need production-safety review.
- Do not use when the task is general database modeling with no migration or rollout action.
Inputs
- Migration files, SQL snippets, schema diff, backfill plan, or rollout notes.
- Database type, table size, traffic patterns, and deployment process if available.
- Rollback expectations and validation commands.
Workflow
- Classify the migration type: schema, data, index, backfill, constraint, or cleanup.
- Identify locking, data loss, long-running query, and compatibility risks.
- Check forward and backward compatibility with application code.
- Recommend validation queries and rollout sequencing.
- State rollback limits honestly.
Output
Produce Markdown with:
- Migration Snapshot
- Risk Map
- Compatibility Review
- Validation Checks
- Rollout Plan
- Rollback Notes
- Open Questions
Validation
- Data loss risks are explicit.
- Locking and runtime impact are considered.
- Rollback is not promised when impossible.
- Validation checks are concrete.
- Unknown table size or traffic is flagged as a risk.