-
Notifications
You must be signed in to change notification settings - Fork 1
Commands
Slash-invoked operations. Simple, deterministic, no configuration. The user types /<name> and gets the same behavior every time.
For the canonical reference, see commands/README.md.
Commands are vendor-specific in shape. There is no single canonical format — each vendor consumes a different file structure.
.claude/commands/<slug>.md
Markdown file. Frontmatter:
---
description: <one-line description shown in /help>
---Body is the prompt that the slash command expands to. Body can include shell snippets in fenced code blocks; Claude executes them with explanation.
.gemini/gemini_cli_config.json
JSON file with a top-level commands object:
{
"commands": {
"<slug>": {
"command": "<shell command to run>",
"description": "<one-line description>",
"directory": "<optional working directory>"
}
}
}The command is a literal shell command, not a prompt. Different paradigm from Claude.
Codex has no separate command primitive. The equivalent is a skill with user-invocable: true and a clear argument-hint:
.codex/skills/<slug>/SKILL.md
These vendors have no slash-command concept. For Kiro use hooks for automation. For Cursor and Windsurf, the equivalent is a rule the agent reads and acts on.
| Question | Answer |
|---|---|
Does the user type /<name> once and get the same result? |
Command |
| Does the user need to make decisions mid-flow? | Skill (interactive) |
| Should it run autonomously without user input? | Agent |
| Should it run automatically on an event? | Hook |
See Automation Decision Framework for the full matrix.
The four commands under this repo's own .claude/commands/ are real, tracked examples:
-
/audit— comprehensive pre-commit check. -
/parity— cross-vendor runtime parity check. -
/sanitize— sanitization wordlist scan. -
/status— skeleton state report.
Read audit.md and sanitize.md for the most substantive examples of the markdown shape.
Designing and reviewing slash commands is owned by the command-author agent.
- Skills · Agents · Hooks — the other three primitives
- Automation Decision Framework — when to reach for a command vs alternatives
- Vendor Matrix — which vendors consume commands and in what shape
Repository · Issues · Roadmap · Changelog · Security · License (Apache 2.0) — © Enovatr Labs
- Philosophy
- Spec-Driven Development
- Agentic Coding Model
- Automation Decision Framework
- Multi-Agent Orchestration
- Two-Tier Docs Pattern
- Multi-Vendor Context Files
- Documentation Structure
- Agent Memory
- Artifact Taxonomy
- PRDs
- Specs
- Agents
- Skills
- Commands
- Hooks
- Prompts
- Rules
- Frontmatter Contracts
- Sanitization