Skip to main content
Slash commands are shortcuts that start with / and perform specific actions inside a Claude Code session. Jinzo supports both built-in commands and custom commands you define yourself.

Built-in Commands

CommandDescription
/compactSummarize and compress conversation history to free up context
/debugEnable debug logging for this session and help diagnose issues (bundled)
/configOpen configuration settings
/simplifyReview change code for reuse, quality, and efficiency, then fix any issues found
/loopRun a prompt or slash command on a reccuring interval.
/contextShow current context usage
/insightsGenerate a report analyzinf your Claude Code sessions
/extra-usageConfigure extra usage to keep working when limits are hit
/reviewReview a pull requestReview a pull request
/heapdumpDump the JS heap to /Desktop

Custom Commands

Custom commands are Markdown files that define reusable prompts. The filename becomes the command name.

Locations

LocationScope
.{your_project}/commands/Project commands — shared via git
~/.claude/commands/Personal commands — available across all projects

Creating a Command

Create a .md file in one of the command directories: .{your_project}/commands/review.md:
---
description: Review code changes for issues
allowed-tools: Read, Grep, Glob
---

Review the recent code changes. Check for:
- Security vulnerabilities
- Performance issues
- Missing error handling
Provide findings as a numbered list with severity ratings.
Then invoke it in a session:
/review

Arguments

Commands support positional arguments with $1, $2, etc., and $ARGUMENTS for the full argument string: .{your_project}/commands/fix-issue.md:
---
argument-hint: [issue-number]
description: Fix a GitHub issue
---
Fix issue #$1. Check the issue description and implement the necessary changes.
/fix-issue 142

File References and Shell Output

Commands can include file contents with @ and shell output with !: .{your_project}/commands/commit.md:
---
allowed-tools: Bash(git add:*), Bash(git commit:*)
description: Create a git commit
---
## Context
- Current status: !`git status`
- Current diff: !`git diff HEAD`
## Config
- Package: @package.json
Create a commit with an appropriate message based on the changes.

Namespacing

Organize commands in subdirectories:
.{your_project}/commands/
├── frontend/
│   ├── component.md      # /component
│   └── style-check.md    # /style-check
├── backend/
│   └── api-test.md       # /api-test
└── review.md             # /review

Frontmatter Options

FieldDescription
descriptionWhat the command does (shown in help)
allowed-toolsComma-separated list of tools the command can use
argument-hintUsage hint shown when listing commands
modelOverride the model for this command