ArcQian-bitArcQian-bit/codex-real-engineer-skills/skills/migration-pilot/SKILL.md

migration-pilot

Skill1 starsChanged 5 months agoMITView on GitHub

Plan and execute framework, dependency, API, database, config, repository, or naming migrations safely. Use when the user asks to upgrade versions, rename projects, move files, change public contracts, migrate schemas, replace libraries, or perform codemods. Do not use for small isolated edits that have no compatibility or rollout risk.

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Run targeted verification after each slice.
line 20
Distinctive:
Update docs and cleanup only after the new path is proven.
line 21
Distinctive:
Add deprecation notes before removal.
line 26
Distinctive:
Keep rollback notes for releases and database changes.
line 27
Distinctive:
Avoid mixing migration with unrelated refactors.
line 28
Distinctive:
Check lockfiles, generated artifacts, and examples.
line 29

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Migration Pilot

Move systems without losing behavior.

Workflow

Inventory every affected surface: imports, config, docs, tests, scripts, CI, generated files, public APIs, and deployment settings.
Identify compatibility constraints and consumers.
Choose migration shape:
- Big bang for tiny private changes.
- Compatibility layer for public or cross-module contracts.
- Dual-write/read or backfill for data migrations.
- Codemod for repeated mechanical edits.
Make the smallest reversible slice first.
Run targeted verification after each slice.
Update docs and cleanup only after the new path is proven.

Risk Controls

Preserve old names temporarily when callers may still use them.
Add deprecation notes before removal.
Keep rollback notes for releases and database changes.
Avoid mixing migration with unrelated refactors.
Check lockfiles, generated artifacts, and examples.

Output

Use:

Inventory:
Migration strategy:
Compatibility plan:
Implementation slices:
Verification:
Rollback:
Cleanup:

Download now (ZIP)

In this repository11 other files it gives its agents.
- docs/llms.txtllms.txt
- llms.txtllms.txt
- docs-keeperSkill
- frontend-polisherSkill
- issue-sherpaSkill
- perf-labSkill
- pr-reviewerSkill
- real-engineerSkill
- release-captainSkill
- repo-cartographerSkill
- security-scoutSkill

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free