Backend Migrations

Database migrations should enforce naming conventions, versioning schemes, and idempotent, transactional scripts with reversible up/down operations. This Skill reviews migration files against your project's established standards—documented in migrations.md—to catch deviations before deployment and ensure consistent schema evolution.

An idempotent migration can run multiple times without causing errors; a reversible migration includes matching up and down operations. Both prevent data loss and enable safe rollbacks. This Skill enforces these patterns along with transactional integrity and logging to ensure migrations are safely deployable and recoverable.

Common pitfalls include missing rollback logic, poor naming, and lack of testing integration. This Skill proactively identifies these issues by checking that migration scripts include proper documentation, testing hooks, rollback capabilities, and adhere to your project's naming and versioning conventions before they reach production.

Yes. This Skill guides the AI to apply uniform coding standards for all migration files, enforcing naming conventions, transactional patterns, and documentation requirements across your project. This guarantees every schema change—whether adding columns or restructuring tables—follows the same vetted approach.

A compliant migration file includes proper naming and version identifiers, idempotent and transactional up/down operations, integration points for testing, rollback capabilities, and clear logging and documentation. This Skill validates these components against your migrations.md standards to minimize deployment risk.

Activate this Skill whenever you develop features requiring schema changes—new tables, columns, indices, or structural updates. It reviews your migration files before deployment to ensure they follow all established coding standards, reducing errors and ensuring safe, reversible database evolution.