migration Skill for Claude: Reversible, Compatibility-Safe Migrations

migration makes your coding assistant plan and run schema, data, API or dependency changes with a rollback path and no surprise deletions.

Installs: 110.6K; on skills.sh
Stars: 116.7K; on GitHub
Files: 1; besides SKILL.md
Updated: Nov 2026; last repo commit

migration tells the assistant to map current readers, writers, data shape, the compatibility window and ownership before it edits. It defines a forward path and a rollback path and keeps existing data. It makes destructive steps explicit and separately authorized, and sequences expand, migrate, verify, then contract. Retries are idempotent and partial failures are visible.

It loads for schema, data, API, protocol, configuration and dependency migrations that need rollback and proof that nothing was lost. It stops after the stage you asked for and does not do a later destructive contraction on its own. It bundles no scripts.

Good for

Developers changing a database schema or API
Teams rolling out changes while old and new versions overlap
Anyone who wants a rollback plan written before the change

Install migration

Claude Code

Copy this prompt.

Install the migration skill in Claude Code. Run this command:

npx skills add https://github.com/juliusbrussee/caveman --skill migration

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

From its listing on skills.sh. Source.

What's in the skill

When it loads

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

Key facts

Author: Julius Brussee (repo owner juliusbrussee)
Repository: juliusbrussee/caveman, folder skills/migration
Installs on skills.sh: 110,601 (as of 2026-11-02)
Repo stars: 116,702 (whole repository, as of 2026-11-02)
License: Apache-2.0
Last repo commit: 2026-11-01
Files in the skill folder: 2 files: SKILL.md and agents/openai.yaml
skills.sh audits: Gen Agent Trust Hub: pass, Socket: pass, Snyk: pass

What it includes

List readers, writers, data shape, compatibility window, ownership
Maps current readers, writers, data shape, the compatibility window and ownership before editing.
Read · Map the current state
Define both paths up front
Defines the forward path and the rollback path.
Forward and rollback
Keep existing data; destructive steps need separate approval
Preserves existing data and makes destructive steps explicit and separately authorized.
Delete · Protect data
Keep operation safe while old and new run together
Keeps mixed-version operation safe where a rollout can overlap.
Mixed versions
Run the stages in that order
Sequences expand, migrate, verify, then contract when applicable.
Write · Expand, migrate, verify, contract
Retries are safe; partial failure is visible
Makes retries idempotent and partial failure observable.
Idempotent retries
Check both paths at each stage; stop after the requested stage
Verifies the old and new paths at the required stages and stops after the requested stage passes.
Runs code · Verify old and new

From the official docs

Permissions

Medium risk

A migration can change or remove stored data if you let it run against a real database. Run it on a copy or staging first, and approve each destructive step yourself.

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

Migrations can touch real data
The skill asks for destructive steps to be explicit and separately authorized. Run it against a copy or staging data first, and keep a backup before any contract step.
It edits code and runs checks
Review the diff and the commands it runs before you apply anything to a shared environment.

Questions

What does the migration skill do?

It makes the assistant treat a migration as a staged, reversible change. It plans forward and rollback paths, keeps existing data, and stops before any destructive step you have not approved.

How do I install migration in Claude Code, the Claude app or Codex?

Use the install box at the top of the page and pick your client. The SKILL.md bundles no scripts and lists no other requirements. The folder also includes an agents/openai.yaml file. The README says your agent picks these work patterns up when a task fits, so you do not need to call it by name.

Does migration need an API key or an account?

No. The SKILL.md asks for no key, login or tool. It is plain instructions for the assistant, and it bundles no scripts.

Is migration safe to use?

It is a short instruction file and bundles no scripts. What it changes is how the assistant behaves when it edits your project, so review the diff and keep your usual git and test setup. The permissions section below lists what to watch.

How is migration different from safe-refactor?

migration changes data, schemas, APIs or dependencies and needs a rollback path and a compatibility window. safe-refactor restructures code while behavior stays identical. Use migration when something stored or shared has to change shape.

Information

updated Nov 2, 2026

Repository: juliusbrussee/caveman
Folder: skills/migration

juliusbrussee/caveman skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 4

migration SKILL.md · github.com
caveman README · github.com
migration openai.yaml · github.com
safe-refactor SKILL.md · github.com