Slash commands

To get started, type / in Bob Shell to see all available commands, or create your own by adding a markdown file to .bob/commands/ or ~/.bob/commands/.

Slash commands provide several key benefits:

• Workflow automation: Turn complex multi-step processes into single commands
• Team standardization: Share commands across your team for consistent practices
• Context preservation: Include project-specific context in every command
• Quick access: Fuzzy search and autocomplete for instant command discovery

When you type / in Bob Shell, a menu appears showing all available commands. These commands come from two sources:

Custom commands extend Bob's functionality by adding markdown files to specific directories:

The filename becomes the command name. For example:

When creating commands through the UI, command names are automatically processed:

• Converted to lowercase
• Spaces replaced with dashes
• Special characters removed
• Leading/trailing dashes removed

Example: "My Cool Command!" becomes my-cool-command

Create a simple command by adding a markdown file:

Add metadata using frontmatter for enhanced functionality:

Bob Shell supports the same slash commands as Bob IDE. While Bob Shell does not provide a dedicated UI for managing commands, you can:

1. Create command files manually in the .bob/commands/ directory in your project or ~/.bob/commands/ in your home directory
2. Edit existing command files with any text editor

Type / in Bob Shell to see a unified menu containing the following types of commands:

1. Unified menu: Custom commands and mode-switching commands appear together
2. Autocomplete: Start typing to filter commands (e.g., /sam shows sample-command-name)
3. Fuzzy search: Find commands even with partial matches
4. Description preview: See command descriptions in the menu
5. Visual indicators: Mode commands are distinguished from custom commands with special icons

Argument hints provide instant help for slash commands, showing you what kind of information to provide when a command expects additional input.

When you type / to bring up the command menu, commands that expect arguments will display a light gray hint next to them. This hint tells you what kind of argument the command is expecting.

For example:

• /mode <mode_slug> - The hint <mode_slug> indicates you should provide a mode name like code or debug
• /api-endpoint <endpoint-name> <http-method> - Shows you need both an endpoint name and HTTP method

After selecting the command, it will be inserted into the chat input followed by a space. The hint is not inserted; it is only a visual guide to help you know what to type next. You must then manually type the argument after the command.

You can add argument hints to your custom commands using the argument-hint field in the frontmatter:

This will display as /api-endpoint <endpoint-name> <http-method> in the command menu.

• Be specific: Use descriptive placeholders like <file-path> instead of generic ones like <arg>
• Show multiple arguments: If your command needs multiple inputs, show them all: <source> <destination>
• Use consistent format: Always wrap placeholders in angle brackets: <placeholder>
• Keep it concise: Hints should be brief and clear

• Use descriptive, action-oriented names
• Keep names concise but clear
• Use hyphens for multi-word commands
• Avoid generic names like help or test
• Note: Names are automatically slugified (lowercase, special characters removed)
• The .md extension is automatically added/removed as needed

• Start with a clear directive
• Use structured formats (lists, sections)
• Include specific requirements
• Reference project conventions
• Keep commands focused on a single task

• Group related commands in subdirectories
• Use consistent naming patterns
• Document complex commands
• Version control your commands
• Share team commands in the project repository

If your commands aren't showing up in the menu:

• Check file location: Ensure custom command files are in .bob/commands/ or ~/.bob/commands/
• Verify file extension: Custom commands must be .md files

When a slash command isn't found, the LLM will see:

• Custom project commands override global custom commands with the same name
• Use unique names to avoid conflicts
• When creating duplicate names through the UI, numbers are appended (e.g., new-command-1, new-command-2)

The slash menu includes mode-switching commands (like /mode code, /mode ask) that fundamentally change the AI's operational mode - they don't just inject text but switch the entire AI context. Custom modes you create also appear as slash commands (e.g., a mode with slug reviewer becomes /reviewer). These mode commands cannot be overridden by custom workflow commands.

Slash commands work identically across both Bob Shell and Bob IDE. This means:

• Commands created in one environment can be used in the other
• The same command syntax and behavior applies in both environments
• Team-shared commands work consistently regardless of which interface team members use