Publish
Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and...
Install
npx skills add code-yeongyu/oh-my-openagent --skill publish -g -a claude-code -y- Repository
- code-yeongyu/oh-my-openagent70.6k
- Category
- DevOps
- Updated
- 3d ago
- License
- See repository
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: <patch|minor|major|explicit-semver>. Triggers: publish, release, deploy, npm publish.
You are the release manager for oh-my-opencode. Execute the FULL publish workflow from start to finish.
CRITICAL: PUBLISH IS SHIP-ONLY, GO STRAIGHT TO THE WORKFLOW
origin/dev is already gated: every PR and push ran CI (test/typecheck/codex-compatibility on 3 OSes), and the publish workflow re-runs those same gates before anything is published.
- NEVER run
/pre-publish-review,/review-work, or any code re-review as part of a publish request. Those run ONLY when the user explicitly asks for a review. - NEVER "fix" code, open PRs, or enter fix-and-re-audit loops during a publish. If the workflow fails or something looks broken, report it and STOP, a publish is the wrong place to repair the tree.
- A publish request with a bump type goes from Step 0 to Step 3 (trigger) in minutes. The only human-scale work is release notes, drafted while CI runs.
CRITICAL: FULL WORKFLOW MEANS THREE RELEASE SURFACES
Publishing is complete only after all release surfaces are verified:
| Release layer | Surface | Required proof |
|---|---|---|
omo pure components | Core/MCP/shared-skill changes inside the published package payload | Release notes call out layer-specific version impact (from the workflow changelog, or /get-unpublished-changes when the user requested it). |
omo opencode | oh-my-opencode and oh-my-openagent npm packages plus platform packages | npm versions and GitHub release exist for the selected bump. |
omo codex | lazycodex-ai, Codex plugin metadata, and code-yeongyu/lazycodex marketplace release | Codex plugin metadata is stamped with the release version, lazycodex-ai publishes, and the LazyCodex repo release is created when the marketplace payload changed. |
The publish workflow must not be reported complete while any of oh-my-opencode, oh-my-openagent, lazycodex-ai, or code-yeongyu/lazycodex verification is unresolved.
