Files
claude-code/commands/README.md
OpenCode Test 2ff7f6b133 Add /export and /mcp-status commands
- /export command to export session data as Markdown or JSON
  - Export for sharing with other Claude instances
  - Include session details, topics, summary, and memory items
- /mcp-status command to check MCP integration health
  - Gmail venv and credentials status
  - Calendar API dependencies
  - Delegation helpers presence
  - MCP server configuration
- Updated shell completions with 15 aliases total
- Test suite now covers 23 tests

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-01 18:47:50 -08:00

93 lines
2.8 KiB
Markdown

# Commands
Slash commands for quick actions. User-invoked (type `/command` to trigger).
## Available Commands
### Top-Level
| Command | Aliases | Description |
|---------|---------|-------------|
| `/pa` | `/assistant`, `/ask` | Personal assistant entrypoint |
| `/help` | `/commands`, `/skills` | Show available commands and skills |
| `/status` | `/overview`, `/dashboard` | Quick status across all domains |
| `/summarize` | `/save-session` | Summarize and save session to memory |
| `/remember` | `/save`, `/note` | Quick save to memory |
| `/config` | `/settings`, `/prefs` | View/manage configuration |
| `/search` | `/find`, `/lookup` | Search memory, history, config |
| `/log` | `/logs`, `/logview` | View and analyze logs |
| `/debug` | `/diag`, `/diagnose` | Debug and troubleshoot config |
| `/export` | `/session-export`, `/share` | Export session for sharing |
| `/mcp-status` | `/mcp`, `/integrations` | Check MCP integrations |
| `/maintain` | `/maintenance`, `/admin` | Configuration maintenance |
| `/programmer` | | Code development tasks |
| `/gcal` | `/calendar`, `/cal` | Google Calendar access |
| `/usage` | `/stats` | View usage statistics |
### Kubernetes (`/k8s:*`)
| Command | Description |
|---------|-------------|
| `/k8s:cluster-status` | Quick cluster health overview |
| `/k8s:deploy` | Deploy applications to cluster |
| `/k8s:diagnose` | Diagnose Kubernetes issues |
### System Admin (`/sysadmin:*`)
| Command | Description |
|---------|-------------|
| `/sysadmin:health` | System health check |
| `/sysadmin:update` | System package updates |
| `/sysadmin:autonomy` | Set autonomy level for session |
## Command Format
```yaml
---
name: command-name
description: What this command does
aliases: [alias1, alias2]
invokes: skill:skill-name # or workflow: or agent:
---
# Command Title
Instructions for Claude when command is invoked.
```
## Command vs Skill
| Aspect | Command | Skill |
|--------|---------|-------|
| **Invocation** | User types `/command` | Claude decides automatically |
| **Discovery** | Explicit | Based on description matching |
| **Use case** | Quick actions, shortcuts | Domain expertise, workflows |
## Directory Structure
```
commands/
├── README.md
├── pa.md
├── gcal.md
├── usage.md
├── programmer.md
├── k8s/
│ ├── cluster-status.md
│ ├── deploy.md
│ └── diagnose.md
└── sysadmin/
├── health.md
├── update.md
└── autonomy.md
```
Namespaced commands use subdirectories (e.g., `k8s/deploy.md``/k8s:deploy`).
## Adding Commands
1. Create `commands/name.md` (or `commands/namespace/name.md`)
2. Add YAML frontmatter with name, description, invokes
3. Write instructions in Markdown body
4. Update `component-registry.json` if needed for routing