migrate

Generate, validate, and apply versioned database migrations with rollback procedures.

Updated Jun 1, 2025
One-click install
npx skills add https://github.com/Yokhan/yokhanFitnessDocsWebsite --skill migrate-yokhan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate
Source: https://github.com/Yokhan/yokhanFitnessDocsWebsite/tree/main/.claude/skills/migrate
Command: npx skills add https://github.com/Yokhan/yokhanFitnessDocsWebsite --skill migrate-yokhan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating database migrations is risky without proper versioning, validation, and rollback mechanics. This skill provides a structured workflow to generate, validate, apply, and rollback migrations to protect data integrity across environments.

Core Features & Use Cases

  • Generate migration files from schema changes (new tables, altered columns, index updates) using your preferred migration tool.
  • Validate migrations for safety, idempotence, and backward compatibility before applying to any environment.
  • Apply migrations with a documented rollback path and testing steps; supports dry runs and staged deployments across development, staging, and production.
  • Use Case: When your app adds a new feature requiring a table, you generate the corresponding migration, verify it, and deploy with a rollback plan if issues arise.

Quick Start

Use the migration workflow to generate, validate, and apply a new migration in a safe, rollback-ready manner.

Frequently Asked Questions about migrate

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

FAQPage Schema
How do I plan and execute database migrations with rollback capabilities?

Database migrations with rollback capabilities are executed by generating deterministic, versioned change scripts, validating them for safety and idempotence, and applying them with a documented rollback path across dev, staging, and production environments.

What is the safest way to apply schema changes across development, staging, and production?

The safest way to apply schema changes is using a structured workflow that enforces versioned migration scripts, validates for backward compatibility, supports dry runs, and documents rollback procedures before deploying across environments.

How do I validate database migration scripts for idempotence and backward compatibility?

Database migration scripts are validated for idempotence and backward compatibility through an automated safety check that reviews the generated change scripts before they are applied to any environment.

Can I generate migration files for new tables and altered columns automatically?

Yes, migration files for new tables, altered columns, and index updates can be generated from schema changes using your preferred migration tool within a structured, safe deployment workflow.

What is the best way to handle data migrations without risking data integrity?

To protect data integrity during data migrations, use a structured workflow that generates deterministic scripts, validates operations for safety, applies changes via staged deployments, and enforces documented rollback procedures.

When should I use a rollback-ready database migration workflow?

A rollback-ready database migration workflow should be used whenever coordinating schema changes, new tables, or data migrations to ensure versioned scripts, idempotent operations, and safe staged deployments across dev, stage, and prod.