migrate SKILL.md skillA
migrate from ramboz/jig is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ramboz/jig/migrate@git:20260731.fd82a12Pins git:20260731.fd82a12 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ramboz/jig
- Path
skills/migrate/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260731.fd82a12, committed Jul 31, 2026
- First version recorded
- Jul 21, 2026
- Size
- 33,443 bytes
- Repository stars
- 7
- License
- MIT
Inventory an existing spec-driven project and apply bounded migrations to jig defaults: `report`, `adopt-layout`, `rename-decisions`, `split-slices`, slice-to-spec, `seed-decisions`, and `copy-machinery`. Use when the user says migrate this project to jig, adopt jig here, this repo already has specs — set up jig, scaffold-init refused — what now; introduce jig to an existing codebase; apply ADR-0004 to my project; migrate flat slices into nested specs; seed the lightweight-decisions home; or…
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
> Spec 008 created this skill from scratch. The deterministic filesystem > walk + verdict logic + report rendering live in `migrate.py`; this > SKILL.md drives the judgment layer (when to invoke, how to interpret > ambiguities, what operations to suggest in what order). ## What this skill does Closes the "already spec-driven" gap that `scaffold-init` doesn't handle: projects that organically grew the same workflow jig codifies but landed on different conventions (folder names, filename prefixes, slice topology). Direct example: a project with `docs/slices/` (flat) and `docs/decisions/` (validator-style) — `scaffold-init` would not detect it as scaffolded and would either refuse confusingly or pollute the tree. `migrate` flips that around: detect existing shape first, then propose a migration plan, then (in later slices) apply the rename / restructure operations. `migrate.py` exposes six subcommands: - `report` — strictly read-only inventory + plan. - `adopt-layout` — validates an existing custom-root corpus and writes only its `scaffold.json` sentinel/config; supports `--dry-run`. - `rename-decisions` — applies ADR-0004's rename. Idempotent; refuses …
Read the whole file at its exact version.
How to install
mdr add ramboz/jig/migrate@sha256:4b14d6c765b6066eThe line at the top of this page pins the label git:20260731.fd82a12, 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.
[](https://markdownregistry.com/a/art_4laxqadnhfm4htb5)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 21, 2026 and Jul 31, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260731.fd82a12 latest | 2026-07-31 | fd82a12 | 33,443 B | A | view · diff |
| git:20260730.1c1583c | 2026-07-30 | 1c1583c | 32,393 B | A | view · diff |
| git:20260730.dd0d350 | 2026-07-30 | dd0d350 | 32,227 B | A | view · diff |
| git:20260730.a03f6c8 | 2026-07-30 | a03f6c8 | 30,094 B | A | view · diff |
| git:20260721.a3d35a4 | 2026-07-21 | a3d35a4 | 29,982 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (33443 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
ramboz/jig · 7 stars · license MIT · pushed 2026-10-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4laxqadnhfm4htb5 GET https://markdownregistry.com/api/v1/resolve?ref=ramboz/jig/migrate GET https://markdownregistry.com/api/v1/blob/4b14d6c765b6066ea99b1a3395a7832836d084168b71ebc8763a5d255c40d70d
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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.