Database Migration

To automate Supabase migrations with RLS, generate sequential migration files enforcing auth.uid() policies, user_id foreign keys, and timestamp columns. This Skill validates schema conventions locally and provides safe push guidance to prevent deployment drift.

Secure Supabase database migration requires enabling RLS with auth.uid() policies, adding a user_id foreign key to auth.users, implementing soft deletes, and including created_at and updated_at timestamp fields on every new table.

To create a Supabase migration file that passes validation, place it in the supabase/migrations directory with the next sequential number, including RLS statements, auditing fields, and user_id constraints to pass local schema checks before pushing.

The Supabase migration generator works for both development and production environments by enforcing consistent schema conventions and security rules, providing local validation and safe push workflows to reduce deployment risk.

Supabase migration validation fails when new tables lack enabled RLS, auth.uid() policies, a user_id foreign key to auth.users, or mandatory created_at and updated_at timestamp fields. Enforcing these rules locally prevents deployment drift.