What problem does it solve? Detecting drift between application models and the actual database schema is error-prone and risky, especially when migrations run against live data. This Skill provides a safe, cache-first workflow to verify schema consistency strictly against the test database. ## Core Features & Use Cases - Cache-First Context Loading: Reads project conventions, testing rules, and open concerns from the local documentation cache before running any checks. - Test-DB-Only Safety: Enforces non-negotiable rules so all checks run via DDEV against the test database, never the live database. - Structured Drift Reporting: Outputs models and tables checked, mismatches in columns, types, indexes, and foreign keys, mapped to specific migration files. - Use Case: After running recent migrations on a Laravel project, ask the assistant to verify the Property model matches the test database schema and receive a safe remediation report without any destructive commands. ## Quick Start Ask the assistant to run a model schema check on the Property model against the test database after the recent migrations.