converting-slash-commands

Converting Claude Code slash commands to OpenCode format involves running a migration script that transforms command definitions from .claude/commands/ to .opencode/command/, updating frontmatter fields like model and tools to OpenCode equivalents while preserving arguments, shell commands, and file references.

The conversion process translates description, model, and tools fields to OpenCode equivalents, adds provider-prefixed models, removes unsupported fields like argument-hint and disable-model-invocation, and converts both Markdown and JSON command representations while preserving argument placeholders and shell execution patterns.

Yes, the migration applies to both project-level commands in .claude/commands/ and user-level commands in ~/.claude/commands/, converting them to .opencode/command/ or ~/.config/opencode/command/ respectively across Markdown and JSON file formats.

The conversion preserves argument placeholders, file references, and shell execution patterns, maintaining functional behavior while updating the structure and frontmatter to align with OpenCode standards and selecting an appropriate agent based on tool usage.

Unsupported fields like argument-hint and disable-model-invocation are removed during conversion, while essential content including arguments, shell commands, and file references are retained and reformatted for OpenCode compatibility.

Yes, the migration process converts Claude Code commands to OpenCode format while supporting subtask and template structures in JSON forms, ensuring advanced command configurations are properly translated.