Agent skill · software engineering · nexu-io
od-code-migration
Default reference pipeline for the code-migration taskKind — code-import → design-extract → token-map → rewrite-plan → patch-edit ↔ build-test devloop → diff-review → handoff.
Why this skill is useful
Adds a complete executable pipeline for code migration with specific stages and conditions that the AI cannot generate on its own.
What it needs
About 1k tokens when loaded. Last updated 2026-08-07. 84,236 stars on the source repository.
What this skill does
od-code-migration (scenario) Spec §1 / §10.1 / §20.3 / §21.3.2 / §23.3.3: the canonical code-migration flow. The pipeline cannot ship an accept decision without a passing build — the patch-edit ↔ build-test devloop is the convergence engine. Default pipeline The scenario uses build.passing && tests.passing as the convergence signal — promoted into the spec §22.4 vocabulary by the build-test atom. Required user inputs A plugin built on this scenario typically declares od.inputs: repoPath (string, required): pulled from od project import. targetStack (form): collected by rewrite-plan. testCommand / buildCommand (string, optional): overrides the inferred package.json scripts in the build-test atom.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nexu-io/od-code-migration