supabase-schema-audit

This Skill audits a Supabase database by running automated per-schema checks across nine canonical schemas to verify RLS policies, primary keys, foreign keys, indexes, and naming conventions, detecting security and integrity gaps before migrations.

To check schema drift, run a pre-flight audit that loops through schemas to verify integrity constraints and access controls before applying any non-destructive, migration-based changes.

Yes, a migration-fix cycle can address missing primary keys and foreign key constraints by generating an explicit change plan and risk assessment, then applying non-destructive migrations to resolve the issues.

Yes, the audit enforces a non-destructive workflow by requiring explicit change plan approvals and recording evidence before any migrations are applied to your PostgreSQL database.

You can verify naming conventions and index gaps by running an automated per-schema audit loop that checks each of the nine canonical schemas individually against established compliance rules.

A formal change plan is required during migration-fix cycles to ensure governance, recording evidence and approvals before modifying any schema integrity, security posture, or database constraints.