command-creator

To create OpenCode custom commands, define a new markdown file in the .opencode/commands directory with YAML frontmatter to configure behavior and metadata, then reference it in opencode.json to automate repeatable tasks across projects.

YAML frontmatter in markdown command templates configures behavior and metadata for OpenCode custom commands, allowing you to specify prompts, references, and execution logic to reduce manual setup and centralize task management.

Managing reusable commands across projects without drift involves organizing markdown command definitions within the .opencode/commands directory, using YAML frontmatter to standardize execution logic and metadata consistently across teams.

Yes, OpenCode supports markdown templates for configuring custom command execution logic. You can use these templates to specify prompts and references, extending OpenCode capabilities by organizing definitions for reuse across teams.

The best way to define reusable tasks in .opencode/commands is to create markdown files with YAML frontmatter that specify prompts and references, ensuring repeatable execution logic is centralized and standardized across your projects.

Yes, you need to reference custom commands in opencode.json after creating them as markdown files in .opencode/commands. This ensures the defined execution logic and YAML frontmatter metadata are properly registered for your project.