Our review

Runs database migrations with safety checks, dry-run previews, and rollback guidance.

Strengths

Systematic preview of pending migrations before execution
Mandatory dry-run for staging and production environments
Status verification before and after migration
Clear rollback support and creation of reverse migrations

Limitations

Requires the `devflow` tool to be installed
Environments are limited to local, staging, and production
Does not support all database types or ORM-specific migrations

When to use it

When you need to apply database migrations safely and reliably across different environments.

When not to use it

For trivial local schema changes or when using a migration tool that is not compatible with `devflow`.

Examples

Staging migration with dry-run

Run /devflow-migrate staging to apply pending migrations to the staging environment, making sure to do a dry-run first and ask for confirmation.

Production migration with confirmation

Apply the pending database migrations to production. Show a warning banner, require explicit 'yes' confirmation, and recommend having a rollback plan ready.

Rollback last migration

The last migration failed. Help me roll it back: check if there is a down migration, or guide me in creating and writing a reverse migration.

name: migrate description: Run database migrations with safety checks, dry-run previews, and rollback guidance allowed-tools: Bash, Read disable-model-invocation: true argument-hint: [local|staging|production]

Database Migration Workflow

Apply database migrations safely for the specified environment.

Usage

/devflow-migrate - Migrate local environment (default)
/devflow-migrate local - Migrate local environment
/devflow-migrate staging - Migrate staging (requires dry-run first)
/devflow-migrate production - Migrate production (requires confirmation)

Arguments

Environment: $ARGUMENTS (defaults to "local" if not specified)

Safety Rules

ALWAYS run dry-run first for staging and production
NEVER auto-execute production migrations without explicit user confirmation
ALWAYS show what will be applied before executing
If any step fails, stop immediately and report the error

Workflow Steps

Step 1: Verify Prerequisites

devflow doctor

Ensure database connectivity is available for the target environment.

Step 2: Check Current Migration State

devflow db status --env <environment> --json

Parse the output to show:

Total migrations
Applied migrations
Pending migrations (list each one)

If no migrations are pending, inform the user and stop.

Step 3: Preview Pending Migrations

Read each pending migration file and summarize what it does:

# For each pending migration file, read and summarize

Explain in plain English what each migration will do (create table, add column, etc.)

Step 4: Dry Run (Required for staging/production)

devflow db migrate --env <environment> --dry-run --json

Show the dry-run results. If there are any errors, stop and help debug.

Step 5: Confirm and Execute

For local:

Proceed automatically after showing the preview

For staging:

Ask user to confirm: "Apply N migrations to staging?"

For production:

Show a warning banner
Require explicit confirmation: "Type 'yes' to apply N migrations to PRODUCTION"
Recommend having a rollback plan ready

devflow db migrate --env <environment> --json

Step 6: Verify Success

devflow db status --env <environment> --json

Confirm all migrations are now applied.

Rollback Guidance

If migrations fail or need to be reverted:

Check if the migration has a corresponding down migration
If not, help the user create a reverse migration:
```
devflow db create revert_<migration_name>
```
Guide them through writing the rollback SQL

Error Handling

Connection refused: Check if database is running, verify DATABASE_URL
Permission denied: Check database user permissions
Migration conflict: Check for concurrent migrations, advisory locks
SQL syntax error: Show the specific line and help fix it

Safe Database Migration

Recommended for