secure-migration-reviewer

To check database migrations for security risks before deploy, review schema and DDL changes for RLS enablement, policy gaps, privilege widening, destructiveness, and rollback adequacy. Forward and rollback migration artifacts plus current code context are required to assess tenant scope and deploy-order safety.

Expand-then-contract deploy order is a migration strategy that separates schema changes into additive and destructive phases to maintain compatibility with running systems. You need it during database migration review to prevent lock-prone alterations and operational downtime when altering tables, columns, or policies.

To validate tenant isolation during a database backfill, verify that data migrations preserve tenant scope and check RLS policy gaps or unsafe defaults. Migration review requires negative tests when authorization changes or grants are involved to ensure tenant-owned tables remain secure.

Migration review does not work without both forward and rollback migration artifacts. Assessing rollback adequacy, operational safety, and privilege changes requires current code and schema context alongside both migration directions to accurately evaluate destructiveness and compatibility.

Destructive DDL operations fail operational safety checks because they introduce irreversible data loss, lock risk, and inadequate rollback paths. Migration review identifies these destructive alterations and verifies whether the provided rollback migration is actually usable before deploy.

You should not rely solely on automated migration review when schema context or current code is missing, as assessing tenant scope, privilege widening, and deploy-order compatibility requires complete forward and rollback artifacts to accurately validate operational safety.