What problem does it solve? Multi-tenant Supabase applications can leak data between tenants when Row-Level Security policies are incomplete or misconfigured, and these flaws often ship to production unnoticed. This Skill audits migration files and policy DDL before deploy, catching tenant isolation failures like missing WITH CHECK clauses, absent FORCE ROW LEVEL SECURITY, and unguarded SECURITY DEFINER functions. ## Core Features & Use Cases - Per-table policy posture audit: Enumerates every tenant-scoped table in the migration set and verifies RLS enablement, FORCE ROW LEVEL SECURITY, and per-operation policy coverage (SELECT, INSERT, UPDATE, DELETE). - Follow-the-data tracing: Traces foreign keys, join tables, materialized views, and audit tables to confirm the policy chain is unbroken across every relationship. - Migration-shaped remediation: Produces concrete CREATE POLICY, ALTER TABLE, and CREATE OR REPLACE FUNCTION statements using actual column names, plus an RLS_AUDIT.md report with severity-ranked findings. - Use Case: Before merging a migration that adds a new tenant-scoped table, run the audit to confirm the table has policies with proper tenant predicates and that no join table creates a leakage path. ## Quick Start Audit the Supabase migrations in this task for tenant isolation gaps and produce a remediation plan for any RLS policy findings.
