What problem does it solve? Managing Drizzle ORM schema changes safely is error-prone: mixing push and migrate corrupts migration history, editing shipped migrations breaks deployments, and experimental dev changes can leak into production. This Skill enforces a disciplined workflow that keeps disposable dev databases separate from the migration history deployed to production. ## Core Features & Use Cases - Dev Iteration Flow: Iterate on the Drizzle schema with pnpm db:push against a disposable dev database, then generate one clean migration only when the schema is final. - Migration Hygiene: Replace unshipped branch-only migrations with a single clean migration, deleting the migration and its snapshot as one unit without hand-editing snapshots. - Production Safety Rules: Enforces forward-fix migrations, staged deployments for renames/drops/NOT NULL changes, and controlled pnpm db:migrate:prod execution before merging to main. - Use Case: You are adding a new column to a table in the Veles monorepo. The Skill walks you through pushing to the dev database while experimenting, generating and reviewing the final migration, resetting the dev database to verify migrations from scratch, and committing schema and migration together. ## Quick Start Ask the assistant to help you change the Drizzle schema and produce a clean migration for deployment, and it will tell you exactly which pnpm database commands to run and when.
