migrate

Plan and execute database schema migrations with UP/DOWN templates.

2|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/ashtonian/llm-init --skill migrate-ashtonian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate
Source: https://github.com/ashtonian/llm-init/tree/main/templates/.claude/skills/migrate
Command: npx skills add https://github.com/ashtonian/llm-init --skill migrate-ashtonian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing and applying database migrations safely is error-prone and risky without a formal workflow. This Skill provides a structured approach to plan, validate, and implement schema changes with rollback support.

Core Features & Use Cases

  • Structured workflow for planning, designing, and validating migrations across environments
  • Generates UP/DOWN migration files with clear templates and verification steps
  • Ensures backward compatibility, idempotency, and zero-downtime deployment patterns
  • Provides deployment runbooks and rollback procedures, plus tenant-aware considerations
  • Supports multi-environment testing and documentation of changes

Quick Start

Run the migrate skill to begin drafting your database migration plan and generate UP/DOWN templates.

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 safe database schema migrations across staging and production?

Database migrations need structured workflows covering design, validation, and rollback to prevent errors. This skill generates deterministic UP/DOWN templates with backward-compatible, idempotent patterns and comprehensive validation steps for coordinating changes across development, staging, and production environments.

What is the best way to generate backward-compatible SQL migrations with rollback support?

Backward-compatible SQL migrations are best generated using deterministic file naming and clear UP/DOWN templates. This approach ensures idempotency, provides deployment runbooks, and includes rollback procedures to safely revert schema changes if needed.

How do you handle zero-downtime database deployments and rollback procedures?

Zero-downtime database deployments rely on backward-compatible, idempotent migration patterns with comprehensive validation steps. This skill provides deployment runbooks and rollback procedures, including tenant-aware considerations, to safely apply schema changes without service interruption.

Can I use this migration workflow for multi-environment testing and tenant-aware schema changes?

Multi-environment testing and tenant-aware schema changes are fully supported by this migration workflow. It covers coordinating schema changes across development, staging, and production environments while providing documentation and tenant-aware considerations for complex deployments.

Why do my database schema migrations fail during production deployments?

Database schema migrations often fail due to missing validation steps, non-idempotent scripts, or lack of rollback support. This skill prevents these issues by enforcing deterministic file naming, backward-compatible UP/DOWN templates, and comprehensive verification before applying changes.