About Custom Commands
Custom commands are user-defined slash commands stored as .md files. They appear in the / autocomplete menu in chat, letting you quickly invoke frequent prompts, templates, or workflows without retyping them.
Custom commands are available in JetBrains 0.428.8+ as a Public Beta opt-in from the Settings page.
Creating a Command
Create the commands directory
mkdir -p .augment/commands
Create a command file
Create .augment/commands/review.md:---
description: Review code for bugs, security issues, and best practices
argument-hint: <file or description>
---
Review the following code carefully. Check for:
1. Bugs and logic errors
2. Security vulnerabilities
3. Performance issues
4. Adherence to project conventions
$ARGUMENTS
Use the command
Type /review in the chat input to invoke your command.
.md) with optional YAML frontmatter:
Frontmatter Fields
| Field | Description | Default |
|---|
description | Brief description shown in the autocomplete menu | First line of the prompt |
argument-hint | Hint for expected arguments, displayed after the command name | None |
model | Override the default model for this command | Default model |
Template Substitution
Commands support template variables that are replaced when the command is invoked:
| Variable | Description |
|---|
$ARGUMENTS | Replaced with any text typed after the command name |
{placeholder} | Prompts the user to fill in the value |
{{placeholder}} | Alternative syntax for placeholders |
Command Locations
Commands can be scoped per-user or per-project:
| Location | Scope | Description |
|---|
<workspace>/.augment/commands/ | Project | Shared with your team via version control |
~/.augment/commands/ | User | Available across all workspaces |
Importing Commands
Augment also discovers commands from other tools for compatibility:
| Location | Source |
|---|
.claude/commands/ | Claude Code (workspace) |
~/.claude/commands/ | Claude Code (user) |
.cursor/commands/ | Cursor |
Namespacing
Organize commands in subdirectories. A file at .augment/commands/frontend/component.md creates the command /frontend:component.
CLI Usage
Custom commands are also available in the Auggie CLI:
# Run a command
auggie command review
# List all available commands
auggie command list
Best Practices
- Use clear names — choose descriptive kebab-case names like
deploy-staging or security-review
- Add descriptions — include a
description in frontmatter for better discoverability in the autocomplete menu
- Use
$ARGUMENTS — make commands flexible by accepting dynamic input
- Scope appropriately — use project commands for team workflows, user commands for personal shortcuts
- Organize with directories — group related commands using subdirectory namespacing
See Also
