punkdev/cc2oc
Add and ship OpenCode support for one Claude Code plugin at a time. Includes core migration to a reviewable `opencode-plugin/` adapter, maintainer-facing docs, and follow-up CI/versioning setup for package publishing or skill-copy drift checks.
92
92%
Does it follow best practices?
Impact
97%
1.25xAverage score across 2 eval scenarios
Passed
No known issues
versioning-and-release.mddocs/
Versioning And Release Guidance
Use this when preparing OpenCode adapter publishing or CI after local migration works.
Discover Version Source
Check, in order:
- Root
.claude-plugin/plugin.json.version. - Nested
plugin/.claude-plugin/plugin.json.version. - Root or plugin
package.json.version. - Existing tags, release notes, changelog, or marketplace docs.
Do not invent a new scheme silently. If one source is clearly authoritative, use it for opencode-plugin/package.json. If sources conflict, ask the maintainer. If none exists, use 0.1.0 for local adapter files and document that publishing needs a version decision.
CI Responsibilities
Good follow-up CI can verify:
opencode-plugin/package.jsonmetadata and entrypoint.- Skill frontmatter and package-local skill copy parity.
- Hook parity tests and MCP config shape tests.
- Existing Claude tests still pass.
- Optional npm publish path after maintainer approval.
CI setup is not part of the initial local migration. Offer it after the adapter and tests exist.