migrate

To safely apply Drizzle schema migrations to a production database, this Skill automates synchronization across PostgreSQL environments using dry-run previews and explicit user confirmation steps to prevent accidental changes.

Syncing Drizzle ORM schema changes across local and production PostgreSQL databases is best handled by automating the migration process with safety checks, ensuring updates to both development and production environments are applied reliably.

Yes, you need Drizzle ORM for schema definitions and the expect utility for interactive TUI automation to properly automate database migrations and handle the required user confirmation prompts.

You should use an automated migration tool for PostgreSQL when updating schema files with new table definitions, preventing dangerous mistakes by ensuring changes are safely applied to both local development and production environments.

Applying Drizzle migrations directly to production fails safely because the Skill enforces dry-run previews and explicit confirmation steps, stopping accidental production database changes before they happen.