migration

Plan reversible schema, data, and API migrations with rollback and compatibility verification.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/bittlinkm/claude-setup --skill migration-bittlinkm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migration
Source: https://github.com/bittlinkm/claude-setup/tree/main/skills/migration
Command: npx skills add https://github.com/bittlinkm/claude-setup --skill migration-bittlinkm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Migrations often break production systems because destructive changes ship without rollback paths, mixed-version compatibility, or proof that existing data survives. This Skill structures any schema, data, API, protocol, configuration, or dependency migration as a reversible, staged transition. ## Core Features & Use Cases - Reversible Planning: Defines both the forward path and the rollback path before any edit, with destructive steps made explicit and separately authorized. - Compatibility-Safe Sequencing: Orders work as expand, migrate, verify, then contract so mixed-version operation stays safe during overlapping rollouts. - Failure Resilience: Makes retries idempotent, partial failures observable, and verifies old and new paths at each transition stage. - Use Case: When adding a required column to a live database table, use this Skill to plan the expand phase (add nullable column, backfill), verify both readers and writers, and stop before the destructive contraction until explicitly approved. ## Quick Start Use the migration skill to plan a reversible migration of our user table schema with rollback steps and verification at each stage.

Frequently Asked Questions about migration

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

FAQPage Schema
How do I plan a database schema migration with rollback?

Define the forward path and rollback path before editing, then sequence the work as expand, migrate, verify, and contract. Keep destructive steps explicit and separately authorized so the migration can be reversed at any stage.

How to migrate an API without breaking existing clients?

Map current readers, writers, and the compatibility window first, then keep mixed-version operation safe while rollout overlaps. Verify both old and new paths at each required transition stage before retiring the old version.

What is the expand and contract migration pattern?

Expand and contract is a sequencing strategy: first expand the system to support both old and new shapes, migrate data and traffic, verify correctness, then contract by removing the old path. It keeps deployments reversible and avoids breaking changes during rollout.

How do I make migration retries safe after partial failure?

Make every migration step idempotent so retries never duplicate or corrupt work, and make partial failures observable through logging or status tracking. This lets you resume from the failed stage instead of restarting blindly.

When should destructive migration steps be executed?

Destructive steps such as dropping columns or removing old endpoints should run only after the new path is verified and separately authorized. The Skill stops after each requested stage passes and never performs later contraction implicitly.