What problem does it solve? Before designing or migrating a database in a brownfield system, teams often lack a trustworthy picture of what actually exists: tables, stored procedures, naming conventions, transaction behavior, and read/write paths are scattered across DDL exports, ORM mappings, and application code. This Skill produces an evidence-backed current-state analysis so DB design decisions are grounded in facts instead of guesses. ## Core Features & Use Cases - Persistence and model inventory: Builds a persistence inventory plus current logical and physical models from DB-unit SQL export files, cross-checked against ORM mappings, migrations, repositories, and raw SQL. - Local rule extraction: Extracts naming rules, table-definition rules (types, lengths, nullability, defaults, concurrency), stored procedure conventions, transaction and isolation behavior, and DDL/query construction rules with explicit confidence levels. - Mismatch and risk detection: Records DDL/ORM/code mismatches, external dependencies, operational risks, and unresolved live-DB verification status instead of silently picking a winner. - Use Case: Before designing a new schema for a legacy C# application, run this Skill against the repository and its SQL script exports to get a reusable current-state report that hands off concrete local rules to the db_design Skill. ## Quick Start Ask the AI to run the db_current_state_analysis Skill on your target repository with the DB-unit SQL export files and source scope to produce a current database state analysis report.
