opencode-commands

Create and manage OpenCode slash commands with templates and argument handling.

7|2|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/jal-co/jalco-opencode --skill opencode-commands-jal-co
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opencode-commands
Source: https://github.com/jal-co/jalco-opencode/tree/main/opencode/.config/opencode/skills/opencode-commands
Command: npx skills add https://github.com/jal-co/jalco-opencode --skill opencode-commands-jal-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and maintain consistent OpenCode slash commands, including templates, argument handling, and workflow routing across projects.

Core Features & Use Cases

  • Define /command shortcuts with templates and placeholders ($ARGUMENTS, $1, $2, @filename)
  • Route commands to specific agents (plan, explore) or inline execution via opencode.json
  • Provide frontmatter options (description, agent, model, subtask) to control behavior and task scope
  • Examples include designing a /review command, explaining how to pass arguments, or building a command that runs tests

Quick Start

Create a new /review command with a description and optional agent routing.

Frequently Asked Questions about opencode-commands

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create custom OpenCode slash commands with argument interpolation?

You can define OpenCode slash commands using templates with placeholders like $ARGUMENTS, $1, and $2. This enables rapid creation of consistent commands with proper argument handling across your projects.

What is the best way to manage local and global OpenCode command definitions?

OpenCode commands can be managed in local project `.opencode/command/` directories, global `~/.config/opencode/command/` paths, or inline within `opencode.json` files, providing flexible configuration scopes for different workflows.

Can I route an OpenCode slash command to a specific agent or model?

Yes, you can route OpenCode commands to specific agents like plan or explore. Use frontmatter options such as description, agent, model, and subtask to control execution behavior and task scope.

How to pass arguments to OpenCode commands using placeholders?

Pass arguments to OpenCode commands using placeholders like $ARGUMENTS for all input, or $1 and $2 for positional values. You can also use @filename to reference files directly within your command templates.

Does OpenCode support frontmatter options for controlling command behavior?

OpenCode supports frontmatter options including description, agent, model, and subtask. These options allow you to precisely control command execution behavior, route tasks to specific agents, and define task scope.

Why define inline OpenCode command definitions in opencode.json?

Defining inline OpenCode commands in `opencode.json` allows immediate execution without separate files. It provides a centralized configuration approach for quick command setup alongside other project settings.