saranskumar Goal
Review migrations so changes can be applied without avoidable production damage.
When to Use
- A schema or config migration is planned.
- Live data or traffic will be affected.
- Rollout and rollback safety are uncertain.
Instructions
- Identify what changes and who is affected.
- Review sequencing, backward compatibility, and rollout order.
- Review rollback feasibility and operator visibility.
- Flag irreversible or data-destructive risks clearly.
Constraints
- Do not approve risky migrations without rollback thought.
- Keep environment-specific differences explicit.
- Treat hidden coupling as migration risk.
Output Format
- migration review
- blockers
- sequencing notes
- rollback and monitoring notes
Examples
- "Review this Postgres migration plan."
- "Is this config rollout safe across environments?"