command-creator

To create repeatable OpenCode commands, add a Markdown file under the .opencode/commands/ directory with a frontmatter header containing name and description, and a body template serving as the executable prompt. This standardizes repetitive workflows across projects.

OpenCode custom command templates require a Markdown file located in the .opencode/commands/ directory. The file must include frontmatter with name and description fields, while the markdown body acts as the reusable prompt template.

Yes, OpenCode command templates can override or extend built-in commands. You can configure them globally or project-locally under .opencode/commands/ to support discoverability and consistency across development teams.

The best way to standardize workflows is generating reusable command templates in .opencode/commands/. This promotes consistency and discoverability of prompts across teams, ensuring standardized execution of repetitive development tasks.

No dependencies are required to generate OpenCode command files. You simply create a Markdown file with frontmatter and a prompt body in the .opencode/commands/ directory to automate repetitive team or individual workflows.

If OpenCode custom commands are not discovered, verify the command files live under the .opencode/commands/ directory and include required frontmatter with name and description fields, as missing these prevents proper template execution and override.