database-migrations

Plans and executes zero-downtime database migrations for Spring Boot with Flyway and Liquibase.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/RogerioSobrinho/codeme-copilot --skill database-migrations-rogeriosobrinho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-migrations
Source: https://github.com/RogerioSobrinho/codeme-copilot/tree/main/skills/database-migrations
Command: npx skills add https://github.com/RogerioSobrinho/codeme-copilot --skill database-migrations-rogeriosobrinho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Load and manage database migrations safely across environments by consolidating best practices for schema evolution using Flyway and Liquibase, ensuring versioned scripts, reliable rollback, and strong testing guidance.

Core Features & Use Cases

  • Standardized migration naming conventions (V{version}{description}.sql) and repeatable scripts (R{description}.sql) to ensure traceability.
  • Guidance on zero-downtime DDL patterns (add nullable columns, backfill, then NOT NULL) and safe rollback strategies.
  • Clear Spring Boot integration tips for configuring Flyway and Liquibase, plus test strategies to validate migrations before production.

Quick Start

Create a new migration using V{version}__{description}.sql following Flyway conventions and run the test suite to verify migrations across environments.

Frequently Asked Questions about database-migrations

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

FAQPage Schema
How do I perform zero-downtime database migrations in a Spring Boot project?

Zero-downtime database migrations in Spring Boot use patterns like adding nullable columns, backfilling data, then applying NOT NULL constraints, managed via Flyway or Liquibase versioned scripts.

What naming conventions should I use for Flyway SQL migration scripts?

Flyway SQL migration scripts should use standardized naming conventions like V{version}__{description}.sql for versioned migrations and R__{description}.sql for repeatable scripts to ensure traceability.

How do I plan safe rollback strategies for database schema changes?

Safe rollback strategies for database schema changes involve using zero-downtime DDL patterns and versioned scripts in Flyway or Liquibase to ensure reliable recovery across multiple databases.

Can I use Liquibase and Flyway together for database migrations?

Liquibase and Flyway are separate migration tools that can be configured for Spring Boot projects. This guidance helps configure either tool to manage versioned scripts and ensure safe schema evolution.

How do I test database migrations before deploying to production?

Testing database migrations before production involves running the test suite to validate versioned scripts and verify schema changes across environments using Flyway or Liquibase configurations.