Command Development

Create slash commands by writing Markdown files with YAML frontmatter defining command metadata, then use dynamic arguments ($1, $ARGUMENTS) and file references (@path/to/file) to pass inputs. Commands execute inline bash with backticks and integrate with agents and plugins via ${CLAUDE_PLUGIN_ROOT} for portable paths.

Yes, inline bash execution lets you run shell commands using backtick syntax to fetch dynamic context, run scripts, or interact with your local environment. This allows commands like /git-status to retrieve real-time information directly within the command workflow.

Use dynamic argument syntax ($1, $2, $ARGUMENTS) to capture user input and @path/to/file syntax to include file contents directly in commands. This enables flexible, context-aware command behavior without manual file selection.

Yes, slash commands integrate seamlessly with plugins, agents, and other Claude Code components using ${CLAUDE_PLUGIN_ROOT} for portable paths and frontmatter configuration. This lets you chain commands with specialized agents for complex workflows like automated code reviews.

Organize commands using Markdown definitions with YAML frontmatter fields, dynamic argument patterns, and error-handling validation logic. This standardizes complex workflows, ensures consistency across commands, and provides quick access to reusable prompts for repetitive tasks.

No, slash commands use simple Markdown-based definitions with YAML configuration, making them accessible for workflow automation without advanced plugin development knowledge. Basic understanding of argument syntax and bash execution patterns is sufficient to get started.