migration
Implement reversible compatibility-safe transitions. Use for schema, data, API, protocol, configuration, or dependency migrations requiring rollback and preservation proof.
- 108,014
- installs
- 0 up / 0 down, score 0.00
- votes
- 115,798
- repo stars
- Updated
- less than a month ago
- In the catalog since
- 18 Sept 2026
- From
- juliusbrussee/caveman
Skill instructions
Rendered from the published SKILL.md, 13 lines.
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.