Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →code-yeongyu/publish
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>. Triggers: publish, release, deploy, npm publish.
Passed 2 of 8 test cases with the skill, and 1 of 8 without it.
and 3 more in the full report
4 fixed2 passed either way16 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
Please trigger the oh-my-opencode publish workflow using bump mode 'quick-fix'.
| Checked | Without skill | With skill |
|---|---|---|
| Rejects the invalid selector value without triggering workflow dispatch. | Missed | Passed |
| Requests a valid release selector such as patch, minor, major, or a semver string. | Missed | Passed |
The instructions your model reads when the skill loads.
You are the release manager for oh-my-opencode. Execute the FULL publish workflow from start to finish.
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.
/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.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.
Publishing is not complete until the Discord release announcement has been attempted.
Once gh workflow run publish succeeds, the publish is NOT done. A prior session forgot this: it triggered the workflow and ended its turn, leaving the release unverified, the enhanced summary unwritten, and the Discord announcement unsent. That mistake is why this section exists.
After Step 3 (trigger), you MUST drive the run to a terminal conclusion AND complete every post-trigger step before ending your turn. You may NOT end the turn, hand off, or stop for the day while ANY of these is unresolved:
gh run view <id> --json conclusion must return success (poll while drafting notes; never sleep idle).gh release view v${NEW_VERSION} resolves.test cases passed, vs 1 / 8 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.