Database Migration Review

Database Migration Review（数据库迁移审查）

Use the section matching the user's language. 使用与用户输入语言一致的章节。

Execution Contract

Default to standard; explicit invocation is required. Complete one primary task by default. Continue an authorized end-to-end workflow within each Skill's permissions; Router remains recommendation-only. Pause for new material decisions or scope, not authorization already given. Validate according to actual risk; security, production, migrations, releases and other high-risk work use audit. Read references/execution-modes.en.md only when mode selection is unclear.

Database Migration Review

Review one concrete migration using repository evidence. Do not execute it or connect to any production system.

Boundary

• Route generic blast radius to change-impact-analysis, implementation planning to safe-change-plan, and edits to safe-fix-implementation.
• Do not infer engine behavior, table size, traffic, replication topology, or maintenance windows without evidence.
• Keep migration, application, configuration, and data unchanged.

Workflow

1. Identify database engine/version, migration framework, up/down operations, affected objects, application versions, deployment order, and available size or traffic evidence.
2. Separate schema change, data migration/backfill, and application rollout phases.
3. Check reversibility, destructive operations, defaults, nullability, casts, indexes, constraints, foreign keys, triggers, and compatibility windows.
4. Assess locks, long transactions, backfill rate, disk growth, replication lag, retries, partial failure, and zero-downtime sequencing.
5. Verify expand/migrate/contract ordering and old/new application compatibility.
6. Recommend backup, dry run, sampling, checksums or invariants, canary/gray rollout, observability, stop conditions, and rollback.
7. Report evidence, severity, impact, confidence, validation, and unknowns without executing or editing.

Output Contract

1. Scope, engine, and rollout phases
2. Evidence
3. Findings with severity, impact, confidence, and phase
4. Data-loss, locking, replication, and compatibility risks
5. Backup, validation, canary, and rollback recommendations
6. Deployment sequence and stop conditions
7. Unknowns

执行契约

默认使用 standard；仅允许用户显式调用。 默认完成一个主任务。用户已授权完整流程时，在各 Skill 权限内连续完成；Router 仍只推荐。新重大决策或超出授权时暂停，不重复索取已有授权。 按实际风险选择验证；安全、生产、迁移、发布等高风险工作使用 audit。模式不明确时才读取 references/execution-modes.zh-CN.md。

数据库迁移审查

基于仓库证据审查一个具体迁移，不执行迁移，也不连接任何生产系统。

职责边界

• 通用影响交给 change-impact-analysis，实施计划交给 safe-change-plan，修改交给 safe-fix-implementation。
• 不得无证据推断数据库引擎行为、表大小、流量、复制拓扑或维护窗口。
• 保持迁移、应用、配置和数据不变。

工作流程

1. 识别数据库引擎/版本、迁移框架、up/down、受影响对象、应用版本、部署顺序及可用容量或流量证据。
2. 分离 schema change、data migration/回填和 application rollout 阶段。
3. 检查可逆性、破坏性操作、默认值、空值、类型转换、索引、约束、外键、触发器和兼容窗口。
4. 评估锁、长事务、回填速率、磁盘增长、复制延迟、重试、部分失败和零停机顺序。
5. 验证 expand/migrate/contract 顺序及新旧应用兼容性。
6. 建议备份、dry run、抽样、校验和或不变量、灰度、可观察性、停止条件和回滚。
7. 不执行或修改，报告证据、严重度、影响、置信度、验证和未知项。

输出契约

1. 范围、引擎与发布阶段
2. 证据
3. 发现、严重度、影响、置信度和阶段
4. 数据丢失、锁、复制和兼容风险
5. 备份、验证、灰度和回滚建议
6. 部署顺序与停止条件
7. 未知项