Skip to content
skillxone

nexu-io/open-design / plugins/_official/scenarios/od-code-migration

od-code-migration

Verified

Default reference pipeline for the code-migration taskKind — code-import → design-extract → token-map → rewrite-plan → patch-edit ↔ build-test devloop → diff-review → handoff.

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

{
  "stages": [
    { "id": "import",    "atoms": ["code-import"] },
    { "id": "tokens",    "atoms": ["design-extract", "token-map"] },
    { "id": "plan",      "atoms": ["rewrite-plan"] },
    {
      "id": "verify",
      "atoms": ["patch-edit", "build-test"],
      "repeat": true,
      "until": "(build.passing && tests.passing) || iterations>=8"
    },
    { "id": "review",    "atoms": ["diff-review"] },
    { "id": "handoff",   "atoms": ["handoff"] }
  ]
}

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.
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 195kUpdated Claude CodeCodexVerifiedInstall
webapp-testinganthropics/skillsToolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.Stars: 195kUpdated Claude CodeCodexVerifiedInstall
browser-testing-with-devtoolsaddyosmani/agent-skillsTests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
ci-cd-and-automationaddyosmani/agent-skillsAutomates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.Stars: 118kUpdated Claude CodeCodexVerifiedInstall