db-migration-check

Dangerous database operations like adding columns with defaults or creating non-concurrent indexes can lock tables during deployment. This Skill analyzes migration files across Alembic, Django, Flyway, Liquibase, Mongoose, and ActiveRecord to identify risky changes, flag them with severity levels, and suggest safer alternatives before you deploy.

Yes. This Skill supports migration analysis across PostgreSQL, MySQL, SQL Server, and MongoDB, working with multiple migration frameworks including Alembic, Django, Flyway, Liquibase, Mongoose, and ActiveRecord to catch dangerous operations regardless of your database platform.

The Skill detects patterns like adding columns with non-null defaults, creating blocking indexes without concurrency flags, dropping columns without backups, and other operations that cause downtime or data loss. It outputs a structured risk report with specific warnings and safe alternatives for each issue.

The Skill generates a JSON artifact at bazinga/artifacts/{SESSION_ID}/skills/db_migration_check.json containing the complete risk report, dangerous operations flagged by priority, safe migration recommendations, and actionable remediation steps for team review and deployment planning.

Your migration files must already exist in your project using a supported framework—Alembic, Django, Flyway, Liquibase, Mongoose, or ActiveRecord. The Skill analyzes pending migrations directly without requiring framework reconfiguration or special setup.

Dangerous migrations lock production tables and risk downtime; safe migrations use concurrent index creation, add columns without defaults first, and perform risky changes during maintenance windows. This Skill explains each risk and proposes safe deployment strategies for typical upgrade scenarios.