← Back to CRM Delivery Team
See how it helps
Review migration rollout
Checks a proposed migration against existing data, coexisting versions, locking and real rollback feasibility.
migration-rollout-review
Team members using this skill
When is it useful?
Use before approving a production schema or persisted-format transition.
What does it help you do?
- Examines existing records and constraints for incompatible assumptions.
- Checks deployment order while old readers and writers remain active.
- Assesses long locks, backfill cost and data recovery limits.
Try asking this
Review a required-column migration on a populated table and identify a compatible, recoverable rollout order. Check existing nulls and writes from an older app version. Place the backfill and validation before the required constraint, with a realistic data recovery plan.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
Migration & Rollout Review
Use this skill when reviewing changes that include database schema migrations, data transformations, storage format updates, or environment configuration changes.
Workflow
- Verify safety against existing production data:
- Never evaluate a migration only against an empty test database. Check what happens when tables already contain existing rows:
- Adding a
NOT NULLcolumn without a safeDEFAULTor backfill step will fail on non-empty tables. - Adding a
UNIQUEconstraint or narrowing a column type will fail if legacy rows contain duplicates or out-of-range values. - Dropping or renaming a column/table while code or views still reference it causes immediate runtime errors.
- Adding a
- Never evaluate a migration only against an empty test database. Check what happens when tables already contain existing rows:
- Check version coexistence and rollout order (Expand & Contract):
- Verify whether the migration and code change can deploy safely:
- Does old code break if the migration runs seconds before the new application process starts?
- Does new code handle legacy rows created before the migration (e.g., nullable fields, older JSON schema versions, missing metadata)?
- Verify whether the migration and code change can deploy safely:
- Audit performance, locking, and rollback safety:
- Check whether missing indexes on new foreign keys or filter columns will cause full-table scans as data grows.
- Flag migrations that rewrite or lock large tables synchronously during request handling without batching.
- Verify whether the change is reversible (or has a documented forward-fix path) if a rollback is required after deployment.
- Coordinate deep database engine specifics with the database and DevOps specialists.
Included files 1
SKILL.md