What problem does it solve? Setting up drizzle-kit migrations involves choosing between generate and push, writing a correct defineConfig, and navigating per-dialect quirks that differ across postgresql, mysql, sqlite, mssql, cockroach, and singlestore. This Skill orients you to that workflow so schema changes are applied safely and predictably. ## Core Features & Use Cases - defineConfig reference: Documents required fields (dialect, schema, out, dbCredentials) with a minimal postgresql example and Turso/libsql guidance. - Generate vs push decision guide: Explains when to write reviewable .sql migration files versus applying DDL directly to a live database, including the missing_hints approval flow for destructive changes. - Per-dialect quirks catalog: Covers dialect-specific behaviors such as SQLite table rebuilds, MySQL type-change confirmations, and MSSQL rename constraints. - Use Case: After editing a Drizzle schema file, use this Skill to decide whether to run generate for a production release or push for local iteration, and to configure .gitattributes so snapshot files stay out of code-review noise. ## Quick Start Load the drizzle-migrations skill and help me configure drizzle.config.ts and decide between generate and push for my PostgreSQL schema changes.
