opencode-commands

OpenCode Custom Commands

📚 Official Docs: For the latest information, always refer to the official documentation: https://opencode.ai/docs/commands/

Expert skill for building, configuring, and troubleshooting OpenCode's custom command system. Covers markdown command files, JSON configuration, prompt placeholders, command options, built-in commands, keybinds, and overriding built-ins.

Overview

OpenCode's custom command system lets you define reusable prompts that execute via slash commands in the TUI (e.g., /test, /review, /deploy). Commands are triggered by typing / followed by the command name in the prompt input.

Custom commands are in addition to the built-in commands like /init, /undo, /redo, /share, /help. Custom commands can also override built-in command names — if you define a custom command with the same name as a built-in, the custom version takes precedence.

Commands support prompt placeholders ($ARGUMENTS, $1, $2, !command``, @filename) for dynamic prompt construction, and options for agent routing, model override, and subagent invocation.

---

Create via Markdown

The primary way to create custom commands is by placing markdown files in the commands/ directory.

Location

Scope	Path
Project	.opencode/commands/
Global	~/.config/opencode/commands/

The file name (minus .md extension) becomes the command name:

File Name	Command
test.md	/test
review.md	/review
deploy-staging.md	/deploy-staging
create-component.md	/create-component

Structure

A markdown command file has two parts:

1. Frontmatter (YAML between --- delimiters) — defines command properties
2. Content (everything after the closing ---) — becomes the prompt template sent to the LLM