Skills juliusbrussee/caveman Caveman
migration
- Use it when
- you're changing a database schema, data format, API, protocol, config or dependency that other code relies on
- It does
- maps who reads and writes the current form, then plans both a forward path and a rollback before editing
- You get
- a migration done in stages, with old and new versions able to run side by side and each stage verified
- Won't
- delete old data or remove the old path unless you separately ask for that step
- Runs
- on its own, whenever the agent sees a task that fits; it's a short list of rules, not a step-by-step guide
Skill 12 of 12 in the Caveman bundle · Before it: safe-refactor
TLDR
Before editing, the agent maps the current readers, writers and data shape, how long old and new versions must coexist, and who owns each part. It defines a forward path and a rollback path, keeps existing data intact, and makes any destructive step explicit and separately authorized. If old and new versions may run at the same time during a rollout, both must keep working. It follows the expand, migrate, verify, contract order: add the new form next to the old one, move over, check, and only then remove the old. Retries must be idempotent, and partial failures visible. It verifies the old and new paths at each stage and stops at the stage you asked for: if you asked only to add the new form, removing the old one is a separate request.
Summarizes the skill at bad48a0.
npx skills add https://github.com/juliusbrussee/caveman --skill migrationskills.sh page · Source on GitHub · All skills from juliusbrussee/caveman
- Installs
- 61,086 on skills.sh, Sep 21, 2026
- Repo stars
- 106,976 juliusbrussee/caveman
- First seen
- Aug 11, 2026 on skills.sh
Weekly values
| Week to | Installs |
|---|---|
| Aug 3 | 0 |
| Aug 10 | 0 |
| Aug 17 | 6,232 |
| Aug 24 | 8,787 |
| Aug 31 | 8,894 |
| Sep 7 | 10,980 |
| Sep 14 | 12,405 |
| Sep 21 | 13,020 |
| Category |
Test-first work, implementation from specs, git hygiene and scope control. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills. |
|---|---|
| Type |
A multi-step process the agent follows: interview, debug, run a TDD loop, review. |
| Effect |
Its own steps create or change files, git state or local tools. |
| Needs |
Instructions only. Works in any agent that supports skills. |
| Publisher |
Everyone else. Unverified vendor claims default to community. |
| Topics |
SKILL.md
From juliusbrussee/caveman at bad48a0. Checked daily, last changed Oct 20, 2026.
Frontmatter
name: migration
description: 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.