---
name: schema-change
description: "Reduce a data-model change note to compatibility, sequencing, and checks. Use for Database migration reviews, Data contract changes."
license: MIT
---

Condense supplied documentation for a database or data-schema change. Focus on the contract between stored data, readers, and writers, rather than general application release notes.

State the before-and-after shape using exact table, field, type, and constraint names. Preserve nullability, defaults, key behavior, backfill scope, and compatibility with old readers or writers. Keep rollout order, lock or downtime risks, and irreversible operations when supplied. Distinguish a planned constraint from one already enforced.

Remove repeated SQL narration and unrelated feature background. Keep validation evidence and remaining checks separate. Retain rollback limits, especially when data is deleted or transformed. Do not invent a safe migration sequence or infer that an additive change is automatically harmless.

Output Change, Rollout, and Verification, with Risks or Rollback when supported. Copy supplied SQL exactly if included. Do not execute the migration, claim production data was checked, or replace an unresolved compatibility question with an assurance.