command-writer

Generate OpenCode command files with Markdown templates and frontmatter.

2|2|Updated Apr 7, 2013
One-click install
npx skills add https://github.com/warpcode/dotfiles --skill command-writer-warpcode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: command-writer
Source: https://github.com/warpcode/dotfiles/tree/main/generic/.config/opencode/skills/command-writer
Command: npx skills add https://github.com/warpcode/dotfiles --skill command-writer-warpcode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Generates custom command files that encapsulate complex workflows into simple /command invocations, integrating with existing skills, agents, and tools.

Core Features & Use Cases

  • Encapsulate workflows into single commands for repeatable use.
  • Reference exact skill/agent names and tools for end-to-end automation.
  • Include dynamic inputs via $ARGUMENTS and robust error handling.

Quick Start

Create a new command template that runs a code-review workflow via multiple agents.

Frequently Asked Questions about command-writer

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

FAQPage Schema
How do I automate complex workflows into single OpenCode commands?

Automate workflows by generating custom OpenCode command files that encapsulate multi-step processes into simple /command-name invocations. The Skill scans your OpenCode configuration, validates dependencies, and writes reusable Markdown templates with dynamic $ARGUMENTS to ~/.config/opencode/command/, eliminating repetitive manual execution.

Can I wire multiple skills and agents together into one command?

Yes. Reference exact skill and agent names within command templates to orchestrate end-to-end automation. The Skill generates Markdown files with proper frontmatter that integrate existing tools and skills, letting you invoke complex multi-agent workflows through a single command.

What's required before creating a reusable command template?

Ensure your OpenCode configuration is in place and all referenced skills, agents, and tools are available in your environment. The Skill validates these dependencies before generating the command file, so prerequisites must exist and be properly configured.

How do I pass dynamic inputs to my custom commands?

Use $ARGUMENTS in your command template Markdown to accept runtime parameters. The generated template structure supports variable substitution, allowing callers to pass inputs that customize workflow behavior on each invocation.

Can I include error handling in automated command workflows?

Yes. Command templates generated by this Skill support robust error handling logic within the Markdown structure. Define conditional steps and fallback behaviors in your template to gracefully handle failures across chained skills and agents.

Where do generated command files get stored?

Generated commands are written to ~/.config/opencode/command/[name].md with complete frontmatter and Markdown formatting. This standard location makes them immediately available as /command invocations within OpenCode.