command-guidelines

Standardize opencode command files with required frontmatter and sections.

Updated Jul 26, 2025
One-click install
npx skills add https://github.com/0serna/dotfiles --skill command-guidelines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: command-guidelines
Source: https://github.com/0serna/dotfiles/tree/main/dotfiles/opencode/skills/command-guidelines
Command: npx skills add https://github.com/0serna/dotfiles --skill command-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures consistency and maintainability when creating, reviewing, or updating opencode command files by enforcing a shared structure and clear documentation.

Core Features & Use Cases

  • Standard frontmatter and required sections (Arguments, Task, Workflow, Rules, Output) to ensure predictable behavior and safety.
  • Guidance for validating new or updated commands against project conventions and avoiding scope creep with non-opsx commands.
  • Real-world use: when introducing a new opencode command, apply this template to enable easy review, reuse, and future updates.

Quick Start

Create or update an opencode command file following the exact frontmatter and section structure described above.

Frequently Asked Questions about command-guidelines

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

FAQPage Schema
How do I standardize opencode command file structure for consistency?

Standardize opencode command file structure by applying shared frontmatter with a name and description, plus mandated Arguments, Task, Workflow, Rules, and Output sections to ensure predictable behavior and maintainability.

What sections are required in opencode command documentation?

Opencode command documentation requires frontmatter containing at least a name and description, along with five mandated body sections: Arguments, Task, Workflow, Rules, and Output.

How do I create a new opencode command file that follows project conventions?

Create an opencode command file by adding frontmatter with a name and description, then populating the Arguments, Task, Workflow, Rules, and Output sections to align with project conventions and avoid scope creep.

When do I need to apply command guidelines to opencode files?

Apply command guidelines when creating, reviewing, or updating non-opsx command files within a project to enforce a shared structure, enable easy review, and ensure future maintainability.

Why does my opencode command file fail project review checks?

Opencode command files fail project reviews when they lack the required frontmatter fields or omit mandated documentation sections like Arguments, Task, Workflow, Rules, and Output.

Can I use these command guidelines for opsx commands?

These command guidelines apply specifically to non-opsx commands within the project, providing a standardized structure to guide development, review, and updates while avoiding scope creep.