command-builder

Create a `command-name.md` file in `commands/` (project) or `~/commands/` (personal) with YAML frontmatter and your prompt. Define commands with XML tags, dynamic context loading, and argument handling. Invoke with `/command-name [args]` to standardize workflows like code review, Git operations, or performance optimization across your team.

Slash commands require YAML frontmatter (at minimum: `description`), XML-tagged body structure, and argument parsing logic. This format enables dynamic context loading and robust handling of optional argument hints, letting you build automation for tasks like automated commits, code analysis, or workflow standardization.

Yes. Build slash commands to automate workflows like staging Git changes, generating commit messages from diffs, running code analysis, or enforcing team conventions. Commands execute with `/command-name` syntax and apply consistent logic across individual and team workflows.

Yes. Slash commands handle optional and required arguments with hint support and include testing hooks. XML structure and YAML frontmatter enable dynamic context loading, letting you pass file content, diffs, or environment state into your command logic.

Slash commands use Markdown files with YAML frontmatter and XML-tagged prompt bodies. This combination provides structured metadata, flexible argument parsing, and clear separation between configuration and execution logic for reliable command behavior.

Slash commands include built-in testing hooks. Create and iterate on `command-name.md` in your local `~/commands/` directory, then invoke `/command-name [args]` to validate output. Once tested, move the file to your project's `commands/` directory for team use.