Use when an old estate of jobs and tables has to move to a new platform, to inventory it, rate it, and write the migration plan with scenarios, acceptance numbers, the parallel run and the rollback.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Migration
The job: from the old estate to a migration plan with scenarios, acceptance numbers, a parallel run and a rollback. It plans, it migrates nothing.
Input: the folder, the inventory or the documentation of the old estate.
## Steps
1. Inventory the old estate: jobs, tables, schedules, owners, consumers.
2. Explain every job in three plain lines: inputs, logic, output.
3. Draw the lineage of the old estate.
4. Rate each job: risk, size, value, dead or alive.
5. Propose the cut list, with the reason for each.
6. Gather the requirements for the new platform.
7. Compare at least two target platforms on the requirements.
8. Propose the migration type per job: lift and shift, re-platform, re-engineer.
9. Design the target: where each kept job lands.
10. Map old to new, one row per old output.
11. Propose the order, in waves, the smallest proven one first.
12. Three scenarios: best, expected, worst, with effort and risk.
13. Define the acceptance numbers, per output, with the tolerance.
14. Plan the parallel run: old and new side by side, every output compared, for how long, before the cutover.
…
The line at the top of this page pins the label git:20261029.2e2b6c2, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_6gblzesrochspinq
GET https://markdownregistry.com/api/v1/resolve?ref=datawithbaraa/claude-code-data-engineering-skills/migration
GET https://markdownregistry.com/api/v1/blob/546556bc74ef3d02a15ad33cdb8bd73565584c007bf26a55c331aa61b0509f97
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
datawithbaraa/claude-code-data-engineering-skills · skills/big-review/SKILL.md · Use once a month, or when the platform feels slow, heavy or cluttered, to review the whole platform from the query logs…
datawithbaraa/claude-code-data-engineering-skills · skills/contract/SKILL.md · Use when a new source is connected or a source changes how it delivers, to write the data contract with the source…
datawithbaraa/claude-code-data-engineering-skills · skills/cost-review/SKILL.md · Use for the monthly cost review of the platform, to see where the compute and the storage money goes, per job, pipeline…
datawithbaraa/claude-code-data-engineering-skills · skills/data-product/SKILL.md · Use when a table is served to consumers, released or changed, to build everything a consumer needs as a data product…
datawithbaraa/claude-code-data-engineering-skills · skills/docs/SKILL.md · Use after a change or a release, to write and refresh the runbook and the how-to guides of the project, so the runbook…
datawithbaraa/claude-code-data-engineering-skills · skills/impact/SKILL.md · Use before you change a table, a column or a function, to see what it is built from, what depends on it, who reads it…
datawithbaraa/claude-code-data-engineering-skills · skills/incident/SKILL.md · Use when a job run failed with an error, to walk the incident from the error to the root cause, the workaround, two…
datawithbaraa/claude-code-data-engineering-skills · skills/knowledge-refresh/SKILL.md · Use after a release, to compare the knowledge Claude Code reads, CLAUDE.md, the standards, the source pages and the…
datawithbaraa/claude-code-data-engineering-skills · skills/metadata/SKILL.md · Use when the metadata of a source has to be built or extended, to describe every table and column, the names and types…
datawithbaraa/claude-code-data-engineering-skills · skills/pr-review/SKILL.md · Use before a pull request or another change goes in, on a file, the current diff or a branch, to review it pass by pass…
datawithbaraa/claude-code-data-engineering-skills · skills/profile/SKILL.md · Use when a new source or new files arrive, to profile them before any data contract or pipeline code is written, the…
prekuter/dryforge · codex/plugin/skills/migration/SKILL.md · Bring an existing codebase into Dryforge, once. Reads the code, asks what code cannot show — business rules, security…
prekuter/dryforge · src/skills/migration/SKILL.md · Bring an existing codebase into Dryforge, once. Reads the code, asks what code cannot show — business rules, security…
prekuter/dryforge · agent-plugin/skills/migration/SKILL.md · Bring an existing codebase into Dryforge, once. Reads the code, asks what code cannot show — business rules, security…
prekuter/dryforge · claude/skills/migration/SKILL.md · Bring an existing codebase into Dryforge, once. Reads the code, asks what code cannot show — business rules, security…
prekuter/dryforge · grok/skills/migration/SKILL.md · Bring an existing codebase into Dryforge, once. Reads the code, asks what code cannot show — business rules, security…
prekuter/dryforge · antigravity/skills/migration/SKILL.md · Bring an existing codebase into Dryforge, once. Reads the code, asks what code cannot show — business rules, security…
