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
maintainer-explanations.mddocs/
Maintainer Explanations
Use these snippets for README, OPENCODE_SUPPORT.md, PR notes, and release-readiness summaries.
Why opencode-plugin/?
opencode-plugin/ is a neutral package root for OpenCode adapter code and package metadata. It keeps generated files separate from existing Claude Code files and avoids taking over the repository root package.
Why Not .opencode/ For Generated Files?
.opencode/ is active project config. Use it only for a documented local dogfooding shim or project-specific OpenCode config, not as the default generated package directory.
Does This Break Claude Code Users?
It should not. Existing Claude files remain migration input unless the maintainer explicitly approves changing Claude behavior. Existing Claude tests should continue to pass.
Why Is MCP Separate?
Claude plugins can bundle MCP servers through .mcp.json or inline mcpServers. OpenCode MCP servers are configured under mcp in OpenCode config, so provide an opencode.jsonc / opencode.json patch separately from the npm plugin package.
What Happens Before Publishing?
The maintainer needs a package name, ownership or org access, a version source, and a publishing path. Run the ci-setup follow-up to inspect existing Claude versioning and propose CI/publishing automation.