oc-migration-ops
Migration and refactor operator for live systems: database migrations (D1 → Postgres, schema overhauls), framework upgrades (Hono v3→v4, React 18→19), auth provider swaps, monorepo restructures, and platform moves (Workers → Vercel). Produces incremental plans with rollback points at every step, executes with verification gates, and validates the end state matches the target spec. ALWAYS trigger on /oc-migrate, /oc-migration, /oc-upgrade, /oc-refactor, /oc-swap, /oc-move-to, /oc-platform-move. Also trigger on "migrate from X to Y", "upgrade to", "swap auth provider", "move database", "restructure the monorepo", "refactor to use", "breaking changes", "deprecation", "end of life". Also covers opchain ecosystem upgrades: "update all skills", "checkpoint protocol upgrade", "bulk update SKILL.md". Trigger when transforming an existing system from one state to another — not greenfield building (oc-app-architect) or documenting what exists (oc-reverse-spec).
Target: React / Next.js. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Migration Ops
- /oc-migrate — Command Reference
- How This Skill Fits the Pipeline
- Migration Types
- Auto-Detection
- Phase 0: Assessment (/oc-migrate assess)
- Step 1: Gather Current State
- Step 2: Define Target State
On first invocation, read references/orchestrator.md and follow its welcome protocol. The "change the engine mid-flight" skill. Fills the gap between oc-reverse-spec ("what I have") and oc-app-architect ("what I want") when the answer is "transform one into the other" — without downtime, without data loss, and with a rollback at every step. This is inherently multi-session work. A database migration plan might span 3–4 conversations. Checkpoint protocol adoption is critical from day one. -- Migration-ops sits between "what exists" and "what should exist" — it's the transformation engine. It does NOT build new features (oc-app-architect) or document existing code (oc-reverse-spec). It transforms running systems from state A to state B. -- Every migration request is classified into one of these types. The type determines which reference playbook to load and which verification strategy to use. | Type | Examples | Risk | Key Concern | |---|---|---|---| | Database | D1 → Postgres, schema overhaul, ORM swap, warehouse engine moves (BigQuery → Snowflake), dbt-model/schema overhauls | HIGH | Data integrity, zero data loss | | Framework | Hono v3→v4, React 18→19, Next.js pages→app router |
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- asfbay-bit/opchain-skills
- Source file
- skills/oc-migration-ops/SKILL.md
- Fixed revision
- 1c7c7bd69a7d875a5dffb419911c24752ca6c285
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: asfbay-bit/opchain-skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T17:01:27.185Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
Apache-2.0. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.