Gemini CLI Tutorial #7 - Custom Commands

Create .gemini/commands directory

Store custom command files in `.gemini/commands/` within your project root, with each command defined as a separate TOML file.

Filename determines command name

The TOML filename becomes the slash command (e.g., `component.toml` creates `/component`), requiring a CLI restart to register new commands.

Required TOML structure

Each file requires a `description` field (shown in CLI autocomplete) and a `prompt` field containing the multi-line instructions sent to the model.

Accessing user input

The `{{args}}` placeholder captures text entered after the command name, enabling dynamic prompts based on user specifications.

Multi-step automated workflows

Commands can chain shell commands, manage git workflows, generate code, create test files, and render previews in a single execution.

Context-aware execution

The example validates clean git state before proceeding, derives kebab-case branch names from descriptions, and only renders components after all tests pass.

Autocomplete integration

Custom commands appear in CLI suggestions with descriptions when typing `/`, and support arrow-key history navigation for quick reuse.

Sandbox approval workflow

Each shell command requires user approval (with 'allow always' option), and the model provides a summary of completed actions at the end.