# Omd:migrate

> Legacy deep-reference writer safety gate. Use for old brand migration requests only to prevent retired section/frontmatter writes until the Core v2 catalog migration pipeline is authoritative.

- Skill: `kwakseongjae/omd-migrate` (Agent Skill)
- Install (CLI): `npx skillmds@latest add kwakseongjae/omd-migrate`
- Raw SKILL.md: https://api.skillmd.com/api/skills/kwakseongjae/omd-migrate/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: kwakseongjae (https://skillmd.com/u/kwakseongjae)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/kwakseongjae/omd-migrate

---


# omd:migrate — catalog write safety gate

`CORE_V2_CATALOG_WRITE_BLOCKED`

Do not mutate `web/references/<id>/DESIGN.md`, its frontmatter, numbered
sections, verification footer, or mirrors. Those files remain readable during
the migration window, but creating more legacy bytes would violate the Core v2
dual-read/single-write contract.

For a provider-free assessment, use the Core migration auditor in check mode.
Do not adopt or overwrite its staged result. A migration candidate keeps the
source DESIGN.md canonical until a graph-backed catalog writer, migrated
consumers, evidence binding, and `dropped_segments=0` acceptance ship together.