database-migrations-sql-migrations

Implement zero-downtime SQL migrations with validation and rollback for PostgreSQL, MySQL, and SQL Server.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/Srujan0798/NRG --skill database-migrations-sql-migrations-srujan0798
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-migrations-sql-migrations
Source: https://github.com/Srujan0798/NRG/tree/main/.claude/skills/database-migrations-sql-migrations
Command: npx skills add https://github.com/Srujan0798/NRG --skill database-migrations-sql-migrations-srujan0798

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SQL database migrations in production are risky; this skill focuses on zero-downtime strategies with strong rollback and validation to preserve data integrity.

Core Features & Use Cases

  • Supports PostgreSQL, MySQL, and SQL Server migration strategies with safe deploy patterns (expand-contract, blue-green, online schema changes).
  • Includes pre/post-migration validation, automated backups, and rollback scripts to maintain data integrity during schema changes across large datasets.
  • Use Case: When migrating a critical schema in a live system, run structured migrations with batched data movement and safe cutover to minimize downtime.

Quick Start

Execute zero-downtime migration plans in your database environments using safe, production-ready scripts and verification steps.

Frequently Asked Questions about database-migrations-sql-migrations

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

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

Zero-downtime SQL migrations use safe deploy patterns like expand-contract, blue-green, and online schema changes with batched data movement and structured safe cutover to minimize downtime during live schema updates.

What is the best way to ensure data integrity during database schema changes?

Ensuring data integrity during database schema changes requires explicit pre/post-migration validation, automated backups, and rollback scripts to maintain safety across large datasets in production environments.

Does this migration approach support PostgreSQL, MySQL, and SQL Server?

Yes, this migration approach supports PostgreSQL, MySQL, and SQL Server by applying expand-contract, blue-green, and online schema change strategies tailored to each database platform's production environment.

How do I write idempotent SQL migration scripts with rollback support?

Idempotent SQL migration scripts with rollback support are generated as production-ready, repeatable executions that include automated backups and pre/post-migration checks to safely revert schema changes if needed.

When do I need expand-contract or blue-green strategies for database migrations?

Expand-contract or blue-green strategies for database migrations are needed when migrating critical schemas in live systems, allowing batched data movement and safe cutover to prevent production downtime.