database-migration

Safely run database migrations by enforcing tool detection, generating dry-runs, checking rollback options, and requiring explicit user confirmation before applying changes. This guardrail process prevents destructive schema alterations.

Preview database migration changes by generating a dry-run output of the proposed schema modifications. This workflow requires migration scope clarity and validates rollback options before executing any actual changes.

This migration guardrail workflow supports Prisma, Alembic, and Django. It automatically detects the correct migration tool from your project and applies the appropriate validation checks across development, staging, and production environments.

Ensure rollback safety during a database migration by enforcing guardrails that require environment confirmation, validate backups, and generate rollback options before executing any schema changes.

Prevent accidental database schema changes in staging by requiring explicit environment confirmation and migration scope clarity. The workflow enforces these guardrails and demands user confirmation before applying any modifications.