Back to skills

Agent Skill

Migration

migration

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

JuliusbrusseeDevOpsGoAiAnthropicCavemanClaudeClaude-codeLlmMemePrompt-engineeringSkillTokens

80K installs

•

juliusbrussee/caveman

•

by Juliusbrussee

Score

8.5

/ 10

Installs

80K

Repo Stars

109.2K

Last Updated

1d ago

Fresh

Quality Ratio

83%

Description

Verified

Language

Go

First Published

Aug 2026

Summary

The Migration agent skill guides an AI agent through implementing reversible and compatibility-safe transitions for schemas, data, APIs, protocols, configurations, or dependencies. This is essential for DevOps professionals, backend engineers, and system architects managing critical infrastructure where data integrity and system uptime are paramount during evolving system architecture. It is a skill with 67K installs, indicating widespread adoption for ensuring system stability during changes. This agent skill instructs the AI to first map current system states, ownership, and compatibility windows, then define explicit forward and rollback paths for any transition. It emphasizes preserving existing data, making destructive steps explicit and separately authorized, and ensuring safe mixed-version operation during rollout. It also guides the agent to sequence operations through expand, migrate, verify, and contract phases, ensuring retries are idempotent and partial failures are observable. Verification of both old and new paths at required transition stages is mandated, with a strict directive to avoid implicit destructive contraction steps.

Skill Definition

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.

How to Use

Use in O-mega

Claude Code

npx skills add juliusbrussee/caveman migration