askill
opencode-commands

opencode-commandsSafety 90Repository

Create and manage OpenCode slash commands. Use for defining /command shortcuts, template syntax, argument interpolation, and workflow composition. Use proactively when user says "create a command", "slash command", "/command", "shortcut for", or asks about command frontmatter options. Examples: - user: "Create a /review command" → design command with description, optional agent routing - user: "How do I pass arguments to commands?" → explain $ARGUMENTS, $1, $2, `!shell`, @file - user: "Make a command that runs tests" → create command with shell interpolation

6 stars
1.2k downloads
Updated 1/31/2026

Package Files

Loading files...
SKILL.md

Create user-accessible slash commands that streamline workflows.

Command Fundamentals

Location

ScopePath
Project.opencode/command/<name>.md
Global~/.config/opencode/command/<name>.md

Commands MAY also be defined inline in opencode.json:

{
  "command": {
    "my-command": {
      "template": "Do the thing with $ARGUMENTS",
      "description": "One-line description"
    }
  }
}

Frontmatter Options

FieldTypeDescription
descriptionstringREQUIRED. Brief description shown in command list
agentstringRoute to specific agent (e.g., plan for read-only research)
modelstringOverride model for this command
subtaskbooleanIf true, runs as background task via task tool

Template Placeholders

PlaceholderExpansion
$ARGUMENTSAll arguments after the command
$1, $2...Positional arguments (space-separated)
`!cmd`Output of shell command (e.g., `!git status`)
@filenameContents of file (e.g., @src/main.ts)

Command Patterns

Simple Command

---
description: Run all tests with coverage
---

Run tests with coverage reporting:
\`!npm run test:coverage\`

Agent-Routed Command

---
description: Research a topic without modifying files
agent: explore
---

Research the following topic thoroughly, gathering context from the codebase and web:

$ARGUMENTS

Workflow Command with Arguments

---
description: Create a new component with tests
---

Create a new React component named "$1" in the $2 directory.

Requirements:
1. Component file with TypeScript
2. Test file with basic render test
3. Index export

Use the existing patterns from @src/components/Button/index.tsx

Background Task Command

---
description: Deep research task (runs in background)
subtask: true
agent: explore
---

Perform comprehensive research on: $ARGUMENTS

Return findings in a structured report.

Best Practices

MUST

  • Keep descriptions under 80 characters
  • Use agent: explore or agent: plan for read-only operations
  • Use subtask: true for long-running operations
  • Include example arguments in the description when helpful
  • Use @file to inject context from existing code

MUST NOT

  • Create commands that duplicate existing tools
  • Use commands for one-off tasks (just ask directly)
  • Forget to test with opencode run "test" after changes
  • Route to agents that don't exist

Command vs Direct Request

Commands are USER shortcuts. Use them when:

  • You repeat the same request pattern frequently
  • You want consistent agent/model routing
  • You need to inject file context or shell output

For one-off tasks, just ask Claude directly.

Validation

After creating a command:

opencode run "test"

Then test with:

/your-command test arguments

Install

Download ZIP
Requires askill CLI v1.0+

AI Quality Score

95/100Analyzed 2/13/2026

A comprehensive and highly actionable guide for creating OpenCode slash commands. It provides precise technical details on file locations, frontmatter configuration, and template interpolation, supported by clear examples and validation steps.

90
95
85
95
95

Metadata

Licenseunknown
Version-
Updated1/31/2026
Publisherjustinlevinedotme

Tags

github-actionsllmtesting