# Database Migration Risk Review

> Use when reviewing schema migrations, SQL changes, data backfills, index changes, or rollout plans for data loss risk, locking, rollback gaps, validation checks, and production safety.

- Skill: `alexzhu0/database-migration-risk-review` (Agent Skill)
- Install (CLI): `npx skillmds@latest add alexzhu0/database-migration-risk-review`
- Raw SKILL.md: https://api.skillmd.com/api/skills/alexzhu0/database-migration-risk-review/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Data & Analytics
- Author: alexzhu0 (https://skillmd.com/u/alexzhu0)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/alexzhu0/database-migration-risk-review

---


# 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

1. Classify the migration type: schema, data, index, backfill, constraint, or cleanup.
2. Identify locking, data loss, long-running query, and compatibility risks.
3. Check forward and backward compatibility with application code.
4. Recommend validation queries and rollout sequencing.
5. 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.