← LeaderboardThe Skill Leaderboard

migration

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

Published by JuliusBrussee ↗JuliusBrussee/caveman

Try your first task

migration

Start a fresh conversation. Replace the highlighted placeholders.

Use migration to implement a reversible, compatibility-safe migration for [current and target system or data shape], accounting for [readers, writers, rollout window, and ownership], and deliver the forward and rollback paths with transition-stage verification; preserve data and present any destructive contraction step for separate authorization.

Required inputs

  • [current and target system or data shape]
  • [readers, writers, rollout window, and ownership]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

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

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.