What problem does it solve? Applications often enforce business invariants only in application code, leaving the database unable to prevent impossible states when other writers (jobs, imports, admin tools) or race conditions bypass that validation. This Skill verifies whether the database itself enforces integrity through real constraints. ## Core Features & Use Cases - Constraint Verification: Checks unique constraints, foreign keys with ON DELETE policies, transactions, cascading rules, soft delete handling, enums, and CHECK/NOT NULL constraints against the actual schema DDL. - Attack Pattern Catalog: Provides concrete failure patterns such as unique bypass via race conditions, orphan foreign keys, soft-delete unique collisions, and partial multi-write transactions. - Evidence-Based Reporting: Classifies findings by confidence level (CONFIRMED, HIGH CONFIDENCE, POSSIBLE, SPECULATIVE) and outputs structured audit reports with exact remediation constraints. - Use Case: When reviewing a schema where usernames are checked for uniqueness only in the request handler, use this Skill to confirm the missing unique index and demonstrate how a concurrent writer can insert duplicates. ## Quick Start Audit my database schema and migrations to verify that unique constraints, foreign keys, enums, and CHECK constraints actually prevent impossible states at the database level.
