What problem does it solve? After any database migration or schema change, it is easy to leave tables without Row Level Security enabled or with missing policies, creating silent security gaps where sensitive HR data (medical info, salaries, personal documents) could be exposed or where the app silently fails to read data. This Skill runs a structured verification suite against pg_policies and pg_class to catch those gaps immediately. ## Core Features & Use Cases - Coverage Verification: Detects tables without RLS enabled and tables with RLS enabled but zero policies across the hr, requests, docs, workflows, audit, notifications, files, performance, and learning schemas. - Sensitive Table Auditing: Verifies that medical_info, personal_documents, and salary-related policies follow the ownership-or-HR-admin pattern required by rule R13. - Functional Impersonation Tests: Simulates an authenticated user via JWT claims to confirm one employee cannot read another employee's protected rows. - Use Case: After creating a new table in the requests schema, run the verification queries to confirm RLS is enabled, policies exist for SELECT/INSERT/UPDATE, and WITH CHECK clauses validate written rows. ## Quick Start Validate the RLS policies on the new table I just created in the hr schema and tell me if anything is missing.
