What is the processing order for command injections?

Injections are processed in a specific sequence: first File injection (@{}), followed by Shell execution (!{}), and finally Argument substitution ({{args}}).

Where are Gemini custom commands stored?

Custom commands can be stored globally in ~/.gemini/commands/ for use across all projects, or locally in .gemini/commands/ for project-specific functionality.

Can I run shell commands inside a Gemini command?

Yes, using the !{command} syntax. This allows you to inject the output of tools like 'git diff' or 'ls' directly into the AI prompt.

How do I handle arguments in a custom command?

Use the {{args}} placeholder within your TOML prompt field. Any text typed after the slash command will be injected into that location.

How do I inject file contents into a command?

Use the @{path/to/file} syntax to automatically read and inject the contents of a file or directory into your command prompt.

Gemini TOML Command Builder

Name: Gemini TOML Command Builder
Author: melodic-software

bymelodic-software

•

Productividad y Flujo de Trabajo

Builds custom Gemini CLI slash commands using TOML syntax to automate repetitive workflows and inject project-specific context.

Acerca de

This skill serves as a comprehensive guide for developers using the Gemini CLI who want to extend its functionality with custom commands. It provides detailed patterns for creating slash commands that can handle user arguments, execute shell commands for real-time data, and inject file contents directly into prompts. Whether you are automating git commit messages, streamlining code reviews, or creating specialized testing tools, this skill ensures your TOML commands are syntactically correct and follow best practices for security and efficiency.

Características Principales

Secure shell output injection using !{} blocks
Dynamic argument handling with {{args}} injection
TOML syntax validation and structure guidance
Hierarchical command namespacing for organized workflows
Local and global file content injection with @{}
1 GitHub stars

Casos de Uso

Automating conventional git commit messages based on staged changes
Creating project-specific code review and documentation helpers
Building custom diagnostic tools that combine shell output and file context

Acerca de

Características Principales

Secure shell output injection using !{} blocks
Dynamic argument handling with {{args}} injection
TOML syntax validation and structure guidance
Hierarchical command namespacing for organized workflows
Local and global file content injection with @{}
1 GitHub stars

Casos de Uso

Automating conventional git commit messages based on staged changes
Creating project-specific code review and documentation helpers
Building custom diagnostic tools that combine shell output and file context