@aexol/opencode-wizard

@aexol/opencode-wizard is a separately releasable OpenCode server plugin package for fetching published skills from the opencode-wizard backend runtime.

Package target

• oc-plugin: ["server"]
• ./server → dist/server.js
• no generated runtime skill directory is published; the plugin stays fetch-only at runtime

Local development

This monorepo still path-loads the same package from ./plugin/opencode-wizard-skills during local OpenCode development.

Backend origin resolution keeps local-first behavior only when the plugin is executing from a local module path/check-out. In that case it still prefers repo .env/PORT, then APP_URL, then falls back to http://localhost:8080. For the packaged/published plugin, the same config values still win when present, but the fallback origin is https://opencode-wizard.aexol.work.

Useful commands:

npm run typecheck
npm run build
npm run release:check

Published package usage

OpenCode server/plugin host can install the published package by package name instead of a repo-local path:

{
  "plugin": ["@aexol/opencode-wizard@latest"]
}

For repo-local development, continue using the local path-based config already documented in this repository.

Release flow

1. Bump version in plugin/opencode-wizard-skills/package.json.
2. Run npm run plugin:skills:release:check from the repo root.
3. If you are following the repo release-tag convention, create Git tag plugin-opencode-wizard-skills-v<version>.
4. Push the release commit/tag so GitLab can run the shared npm public publish job.

The CI publish job comes from ci/templates/node/npm-publish-public.yml, stays manual on the repo deploy stage, runs from plugin/opencode-wizard-skills via APP_ROOT, builds the package with npm run build --if-present, deletes the inherited @aexol GitLab registry override, and then publishes @aexol/opencode-wizard with npm publish --access public --registry https://registry.npmjs.org/.