Skip to main content

​
About Custom Slash Commands

Custom slash commands let you create reusable prompts stored as Markdown files that Auggie can run. You can organize commands by scope (workspace or user) and use directory structures for namespacing.

​
Syntax

​
Parameters

​
Command Types and Locations

Custom commands are stored in markdown files and can be placed in multiple locations with a specific order of precedence:

​
Command Locations (in order of precedence)

  1. User Commands: ~/.augment/commands/<name>.md (user)
  2. Workspace Commands: ./.augment/commands/<name>.md (workspace)
  3. Claude Code User Commands: ~/.claude/commands/<name>.md
  4. Claude Code Workspace Commands: ./.claude/commands/<name>.md
  5. Agents User Commands: ~/.agents/commands/<name>.md
  6. Agents Workspace Commands: ./.agents/commands/<name>.md

​
User Commands

Commands available across all your projects. These are user-wide and persist across different workspaces. Location: ~/.augment/commands/

​
Workspace Commands

Commands stored in your repository and shared with your team. These are workspace-specific and can be committed to version control. Location: ./.augment/commands/

​
Claude Code Compatibility

Auggie automatically detects and supports commands from ./.claude/commands/ for compatibility with existing Claude Code setups. This allows teams already using Claude Code to continue using their existing command libraries without modification. Location: ./.claude/commands/ and ~/.claude/commands/ Migration: While ./.claude/commands/ is supported for compatibility, we recommend migrating to ./.augment/commands/ for new projects to maintain consistency with Auggie’s naming conventions.

​
Features

​
Namespacing

Organize commands in subdirectories. Commands from nested directories can be accessed using the namespace:command syntax, where the namespace corresponds to the subdirectory name. For example, a file at .augment/commands/frontend/component.md creates the command /frontend:component. Conflicts between user and workspace level commands are not supported and will be defined in order of precedence above.

​
Arguments

Pass dynamic values to commands.

​
Frontmatter

Command files support frontmatter for metadata: File: ~/.augment/commands/deploy-staging.md

​
Command Line Execution

We also provide the ability to execute custom commands from the command line using the auggie command <your_command> or list them with auggie command list. For complete command-line reference, see CLI Reference for Custom Commands.
Custom commands appear in the help output with their descriptions:

​
Custom commands vs. skills

Custom slash commands and skills are separate features that share the same /<name> invocation surface in interactive mode: Both appear in the slash-command menu in interactive mode. Built-in slash commands take precedence over a custom command or skill that uses the same name, so pick names that do not collide with the commands listed in Interactive Mode Slash Commands.

​
Example Commands

For ready-to-use examples of custom slash commands, including code review templates, bug fix guides, and feature implementation plans, see: Custom Commands Examples

​
Best Practices

  1. Use kebab-case naming for command names (e.g., deploy-staging, run-tests)
  2. Keep names descriptive but concise, avoiding spaces and special characters
  3. Use meaningful prefixes for related commands (e.g., deploy-staging, deploy-production)
  4. Include clear descriptions in frontmatter for better discoverability
  5. Break complex workflows into numbered steps for clarity
  6. Use user commands (~/.augment/commands/) for personal workflows across all projects
  7. Use workspace commands (./.augment/commands/) for team-shared, project-specific tasks
  8. Organize with subdirectories for related command groups using namespacing
  9. Document command purpose and expected outcomes clearly
  10. Version your commands when making significant changes

​
See Also