Migration

Implement reversible compatibility-safe transitions. Use for schema, data, API, protocol, configuration, or dependency migrations requiring rollback and preservation proof.

Julius Brussee Updated 120k repo stars
Caveman Learn report: a summary and savings cards on the left; the biggest places tokens go, with one fix opened, and a chart of how full sessions get on the ri

File contents

Migration

Map current readers, writers, data shape, compatibility window, and ownership before editing.

  • Define forward path and rollback path.
  • Preserve existing data; make destructive steps explicit and separately authorized.
  • Keep mixed-version operation safe where rollout can overlap.
  • Sequence expand, migrate, verify, then contract when applicable.
  • Make retries idempotent and partial failure observable.
  • Verify old and new paths at required transition stages.

Stop after requested stage passes; do not perform later destructive contraction implicitly.

JuliusBrussee/caveman commit 7d1f2dcb08

Frequently asked questions

npx get-skill add juliusbrussee/migration