create-command_skill

Overview

This skill creates and manages commands for the code-forge application. It generates .md command files with YAML frontmatter and a markdown body placed in the project <cwd>/.forge/commands directory so forge can discover and run them.

How this skill works

The skill scaffolds or edits command files that include required YAML frontmatter (name, description) and a list of actionable steps. Steps can include special tags (<lint>, <test>, <shell>) on their own lines to wire automated linting, testing, or shell tasks into forge workflows.

When to use it

• Add a new workflow or utility that should be invocable from forge
• Modify an existing command to add steps, tags, or fix metadata
• Standardize command names and descriptions to match naming rules
• Convert manual runbooks into executable command files
• Create automated checks that run linting and tests before commits

Best practices

• Place every command file in <cwd>/.forge/commands and name it {command-name}.md
• Use lowercase, verb-based names with hyphens (e.g., run-tests)
• Keep descriptions concise and describe what the command does, not how
• Write steps as bullet points starting with an action verb and present tense
• Put tags on their own line after the step and include complete, executable commands

Example use cases

• Create a check command that runs formatting and tests using <lint> and <test> tags
• Add a git-workflow command that stages changes, runs pre-commit checks, commits and pushes
• Author a cleanup command that removes build artifacts with <shell> commands
• Write an update-docs command to regenerate and verify documentation builds
• Draft a multi-step pr-description command to inspect PRs and update titles