skills/release/SKILL.md
Automated release workflow for OpenCode Hubs
npx skillsauth add Thomashighbaugh/opencode releaseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Automate the release process for OpenCode Hubs.
/release <version>
Example: /release 2.4.0 or /release patch or /release minor
Execute these steps in order:
Update version in all locations:
package.jsonsrc/installer/index.ts (VERSION constant)src/__tests__/installer.test.ts (expected version).opencode/plugins/plugin.json.opencode/plugins/marketplace.json (both plugins[0].version and root version)docs/AGENTS.md (<!-- OAS:VERSION:X.Y.Z --> marker)README.md (version badge and title)npm run test:run
All 231+ tests must pass before proceeding.
git add -A
git commit -m "chore: Bump version to <version>"
git tag v<version>
git push origin main
git push origin v<version>
npm publish --access public
gh release create v<version> --title "v<version> - <title>" --notes "<release notes>"
| File | Field/Line |
|------|------------|
| package.json | "version": "X.Y.Z" |
| src/installer/index.ts | export const VERSION = 'X.Y.Z' |
| src/__tests__/installer.test.ts | expect(VERSION).toBe('X.Y.Z') |
| .opencode/plugins/plugin.json | "version": "X.Y.Z" |
| .opencode/plugins/marketplace.json | plugins[0].version + root version |
| docs/AGENTS.md | <!-- OAS:VERSION:X.Y.Z --> |
| README.md | Title + version badge |
tools
Create valid, type-safe TypeScript tools for OpenCode — generates correct boilerplate, typed interfaces, and handler stubs. Use when building new tools for global config or per-project .opencode/tools/.
testing
Explore multiple solution branches in parallel, evaluate each, and recommend the best path. Use when the user explicitly invokes /ideation tree-of-thoughts or asks for "tree of thought" / "branching exploration".
testing
Run multiple independent reasoning passes and find consensus. Use when the decision is critically important, the stakes are high, or the user explicitly requests "run it multiple times" / "check consistency" / "self-consistency".
testing
Optimization by PROmpting — generate candidate prompt variations, test each against a benchmark, and report the best performer. Use when the user invokes /ideation opro or asks for "prompt optimization" / "OPRO".