Skip to content

aktonay/skillz / skills/efficiency/migration

migration

Unverified

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.

receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 318kUpdated Claude CodeCodexUnverifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 318kUpdated Claude CodeCodexUnverifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 318kUpdated Claude CodeCodexUnverifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 318kUpdated Claude CodeCodexUnverifiedInstall