Question 1

How do I add a custom command to the Gemini CLI with this extension?

Accepted Answer

Create a TOML file in the commands directory (global or project-specific), define a description and prompt with placeholders like {{args}}, and the CLI will recognize it. For example, the gen.toml file shows how to generate unit tests using Jest.

Question 2

Will installing this overwrite my existing Gemini CLI settings?

Accepted Answer

Yes, the installation scripts use rsync to copy files, which can overwrite configurations with the same names. It's recommended to back up your .gemini directory first to avoid data loss.

Question 3

Is this extension better than creating my own Gemini CLI configs from scratch?

Accepted Answer

It provides a curated starting point with practical templates, saving time for common use cases. However, building from scratch offers more control and avoids dependency on external repositories for updates.

Question 4

Can I use this with a team to share configurations?

Accepted Answer

Yes, you can clone the repo into shared projects or version control, but since it's a personal collection, consider forking it for team maintenance to ensure stability and customization.

Question 5

How does the GEMINI.md file work with project context?

Accepted Answer

GEMINI.md files are loaded hierarchically from the current directory up to the root, providing instructions to the AI model. You can modularize context using imports like @./path/to/file.md for better organization.

Question 6

What happens if the Gemini CLI updates and breaks these configurations?

Accepted Answer

The extension might become incompatible, as it relies on the CLI's structure. You'd need to manually update files or wait for the repository owner to patch them, which isn't guaranteed.

gemini-cli-extension

What is gemini-cli-extension?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions