data-migration-safety

What problem does it solve?

It prevents high-risk database changes by reviewing migrations for reversibility, locking behavior, safe backfills, idempotence, constraint/foreign-key rollout, and Supabase RLS correctness so teams avoid outages and data integrity incidents.

Core Features & Use Cases

• Migration safety checklist enforcement: evaluates every migration for required structure (up/down), lock duration risks (e.g., ACCESS EXCLUSIVE), and rollback feasibility.
• Operational migration guidance: flags patterns like non-concurrent index creation, unbatched backfills, and non-idempotent SQL constructs, and recommends safer phased approaches.
• Supabase-specific RLS review: verifies RLS is enabled for new tables/policy changes, ensures per-operation policies exist, and catches service-role bypass risks.
• Risk-aware guidance for regulated data: applies special severity expectations when audit-log integrity or PHI compliance is implicated.
• PR-oriented output: produces actionable BLOCKING|WARN|NIT findings with location, class, risk, estimated impact, fixes, and tests.

Quick Start

Use the data-migration-safety skill on your pull request that modifies migrations, SQL schema files, Supabase migrations, or any schema/RLS-related changes so it can produce a safety verdict for each risky statement.