💡 What Exactly Are Auggie CLI Custom Slash Commands?
Think of custom slash commands as reusable, programmable prompts stored as simple Markdown files.
They let you automate repetitive dev tasks — from reviewing pull requests to deploying to staging and even scafolding new projects — all with one simple command like:
/setup-goYou can make them global (for personal productivity) or workspace-specific (for team collaboration), meaning your entire dev workflow is just a few keystrokes away.
Follow these steps to setup your first custom slash command.
🧩 Step 1: Understanding the Syntax
Custom commands follow a simple structure:
/command-name [arguments]Command name = your Markdown file nameArguments = optional inputs for flexibility
Example:
🗂️ Step 2: Where to Store Your Commands
Where you save them determines who can use them:
Location | Scope | Example |
|---|---|---|
| Global (User) |
|
| Project (Team) |
|
| Claude-Compatible |
|
💡 Migrating from Claude? Auggie detects and supports your old command structure automatically.
🛠️ Step 3: Create Your First Command
Global Command Example:
mkdir -p ~/.augment/commands
echo "Review this code for security vulnerabilities:" > ~/.augment/commands/security-review.md
Workspace Command Example:
mkdir -p .augment/commands
echo "Analyze this code for performance issues:" > .augment/commands/optimize.md
Boom. You’ve just automated your first task.
🔄 Step 4: Add Arguments for Flexibility
Make commands dynamic by accepting parameters.
Command definition:
echo 'Fix issue following our coding standards' > .augment/commands/fix-issue.md
Usage:
/fix-issue 123
The argument 123 can represent an issue ID or PR number — Auggie handles it intelligently.
🧾 Step 5: Enhance Commands with Frontmatter
Add metadata for better organization and discovery:
---
description: Initialize a new Go project with minimal scaffolding
argument-hint: [project-name]
model: claude-haiku-4-5
---
# Set up a minimal Go project structureFrontmatter helps others understand (and reuse) your commands instantly.
💻 Step 6: Run Commands from the Terminal
Execute or explore your commands directly from the CLI:
auggie command list
Get quick command summaries, argument hints, and usage details in seconds.
🧭 Step 7: Organize with Namespaces
Group related commands with folders and namespaces.
Example:
./.augment/commands/frontend/component.md
Now you can call it with:
/frontend:component
A tidy workspace = a happier team.
🧠 Pro Tips for Power Users
✅ Use kebab-case: deploy-staging, run-tests
✅ Keep names short but descriptive
✅ Prefix by function: deploy-, review-, test-
✅ Use subdirectories to organize commands logically
✅ Document your commands with frontmatter for clarity
🌟 Take It Further
Explore even more ready-made command templates and automation examples in the official docs: Custom Commands Examples
Minimize AI coding model hallucinations and keep focused context throughout your projects with my custom 👉 AI Coding Agent Framework rules.
Start building your Auggie CLI automations today — and turn your terminal into a productivity engine.
