migration-patterns

Plan and execute zero-downtime Elixir/Phoenix database migrations with reversible rollbacks.

1|1|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/layeddie/ai-rules --skill migration-patterns-layeddie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migration-patterns
Source: https://github.com/layeddie/ai-rules/tree/main/skills/migration-patterns
Command: npx skills add https://github.com/layeddie/ai-rules --skill migration-patterns-layeddie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Zero-downtime database migrations for Elixir/Phoenix apps, enabling safe schema changes and reversible rollbacks without service disruption.

Core Features & Use Cases

  • Safe zero-downtime migrations with backward-compatible schema changes
  • Reversible migrations and rollback planning
  • Batch data migrations and performance-conscious strategies

Quick Start

Plan and execute a zero-downtime migration for the users table by adding a nullable column, creating an index, and validating the rollout in staging.

Frequently Asked Questions about migration-patterns

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

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

Zero-downtime migrations in Elixir Phoenix require backward-compatible schema changes, reversible migration patterns, and batched data processing to avoid service disruption during production rollouts.

What is the best way to plan a rollback strategy for Phoenix database schema changes?

A rollback strategy for Phoenix schema changes uses reversible migration patterns and best-practice sequencing to minimize risk, ensuring you can safely revert deployments without losing data integrity.

Can I run batch data migrations with health checks in a staging environment?

Yes, batch data migrations with health checks are applicable across production-like environments and staging, validating the rollout sequencing to ensure safe, performance-conscious data processing.

When do I need backward-compatible changes for Elixir database migrations?

Backward-compatible changes are needed for Elixir database migrations when altering production schema, allowing new and old application versions to run simultaneously during zero-downtime deployment transitions.

Does this approach support CI pipelines for Phoenix reversible migrations?

Yes, zero-downtime migration patterns support CI pipelines, enabling automated validation of backward-compatible schema changes and rollback sequencing before deploying to production-like environments.