Commands
Commands are reusable prompts that map to slash commands in tools with native command support. For tools without a native command surface, AgentsMesh either embeds them as projected skills with round-trip metadata or skips command generation — exact per-target behavior is documented in the supported tools matrix.
File format
Commands live in .agentsmesh/commands/ as Markdown files with YAML frontmatter.
---description: Create a conventional commit from current changesallowed-tools: - Read - Bash(git status) - Bash(git diff) - Bash(git add) - Bash(git commit)---
Review the current git changes. Analyze what was modified and why.Draft a conventional commit message (feat/fix/refactor/test/docs/chore scope).Stage the relevant files and commit.The filename (without .md) becomes the slash command name. The above file at commands/commit.md becomes /commit in Claude Code, /commit in Cursor, etc.
Frontmatter reference
| Field | Type | Description |
|---|---|---|
description | string | Short description shown in command menus. |
allowed-tools | string[] | Tools the command is allowed to use when invoked. Uses the same tool name format as permissions. |
Tool-specific behavior
See the Commands row in the supported tools matrix for per-target support levels (native, embedded, or unsupported).
Example commands
Code review
---description: Review the current diff for code quality, security, and correctnessallowed-tools: - Read - Grep - Glob - Bash(git diff) - Bash(git log)---
Review the current git diff. Check for:1. Logic errors and edge cases2. Security vulnerabilities (injection, XSS, auth bypasses)3. Missing tests4. Naming and readability issues5. Performance concerns
Provide a structured review with severity levels: Critical, Major, Minor.Documentation update
---description: Update README and inline docs to reflect recent changesallowed-tools: - Read - Edit - Bash(git diff HEAD~1)---
Review the recent changes in git. Identify what new features, config options,or CLI flags were added. Update README.md and any affected inline documentationto reflect these changes. Keep language concise and developer-focused.Disabling projection for a target
To prevent commands from being projected as skills on a specific target, use the conversions section in agentsmesh.yaml:
conversions: commands_to_skills: codex-cli: false # skip codex-cli instead of embedding