database-migration

Automates database migrations with Flyway schema versioning and blue-green deployments.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/ivegamsft/work-tracker --skill database-migration-ivegamsft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-migration
Source: https://github.com/ivegamsft/work-tracker/tree/main/.agents/skills/database-migration
Command: npx skills add https://github.com/ivegamsft/work-tracker --skill database-migration-ivegamsft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires flyway, liquibase, sql, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates database migrations, ensuring zero downtime, and provides robust strategies for schema versioning, blue-green deployments, and rollback.

Core Features & Use Cases

  • Zero-Downtime Patterns: Implement expand-contract patterns for seamless schema changes.
  • Blue-Green Deployments: Transition between database instances without service interruption.
  • Rollback Strategies: Safely revert to previous database states in case of errors.
  • Schema Versioning: Use Flyway for managing database schema changes and rollbacks.
  • Use Case: Migrating from one database schema version to another while maintaining service availability.

Quick Start

Run the 'database-migration' skill to perform a blue-green deployment on your database instance.

Frequently Asked Questions about database-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform zero-downtime database migrations in production?

Zero-downtime database migrations use expand-contract patterns to apply schema changes without service interruption. This approach separates schema expansion from contraction phases, ensuring continuous availability during production deployments.

What is the best way to roll back schema versioning changes if errors occur?

Rollback strategies for schema versioning safely revert databases to previous states after erroneous migrations. Using Flyway, you can manage database schema changes and execute controlled rollbacks to maintain production stability.

Does Flyway support blue-green deployments for database instances?

Yes, Flyway supports blue-green deployments by managing schema versioning across transitional database instances. This allows you to shift traffic between environments without service interruption during database migrations.

Can I use Liquibase instead of Flyway for automated schema versioning?

Yes, Liquibase is supported alongside Flyway for automated schema versioning tasks. Both tools manage database migrations, allowing you to choose based on your existing SQL workflow and compatibility requirements.

When do I need an expand-contract pattern for database schema changes?

The expand-contract pattern is needed when migrating between database schema versions while maintaining service availability. It expands the schema first, migrates data, then contracts old structures, preventing downtime.