OpenCode: skills not exposed as slash commands after install

[lucabattistini]

Problem

When installing the compound-engineering plugin to OpenCode, no slash commands are written to ~/.config/opencode/commands/. All 54 skills are correctly copied to ~/.config/opencode/skills/, but since the plugin ships no commands/ directory, convertClaudeToOpenCode produces an empty commandFiles array.

The result: users cannot invoke /ce-work, /ce-plan, /ce-debug, etc. in OpenCode, even though those skills are installed. The skills are only reachable via the skill tool call — not as first-class slash commands.

Expected behaviour

Each installed skill should be available as a /ce-<name> slash command in OpenCode, mirroring the experience Claude Code users have natively.

Root cause

convertClaudeToOpenCode only reads from plugin.commands to build commandFiles. The CE plugin has no commands/ directory, so the output is always empty for this plugin.

Fix

PR #776 adds convertSkillsToCommands() which generates one OpenCodeCommandFile stub per skill. Explicit commands take priority when names collide (addressed in a follow-up commit after review feedback).

[rapcal]

My 2 cents - opencode defaults to not showing skills as slash commands, but you can select them via ctrl + p, selecting "skills" and filtering for what you want.

Then they're inserted as slash command.

[lucabattistini]

Fair point, but that's not the same DX I'd get with Claude Code for example. There, custom commands would be available directly as slash commands, always visible in the completion, with immediate discovery.
Opencode does support custom commands though (which is what matters), and my PR integrates the Compound Engineering plugin exactly that way 😊