Skip to content

ByteQuester/custom-slash-commands-gemini-cli

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Gemini CLI Project Commands

License: MIT

A self-contained, portable set of custom slash commands and MCP servers for the Gemini CLI. Drop the .gemini/ directory into any project (or clone this repo) and run from the project root.

Structure

  • .gemini/commands: Custom command definitions as .toml files
  • .gemini/mcp/servers.json: MCP server definitions used by the commands
  • .gemini/mcp/servers/*: Local FastMCP servers (Python) launched via start-stdio.sh

MCP Servers (included)

Server Description
filesystem Local filesystem access for read/write where permitted
fastmcp-local Research, planning, and notes prompts (no code execution)
database-tools Database schema/design and SQL optimization prompts
dev-tools Development prompts: review, architecture, API, Docker, testing
custom-tools Broad set of prompts: docs, ops, perf, refactor, security, etc.

Optional MCP servers used by some commands (configure in your client or add to servers.json if needed): fetch, postgres, sqlite, docker, github.

Available commands

Commands are provided in two ways:

  • Local slash commands from .gemini/commands
  • MCP prompts exposed by the configured servers (often surfaced as slash commands by the client)

Local slash commands (.gemini/commands)

  • /db design, /db optimize
  • /env check
  • /notes capture
  • /plan strategy
  • /research web, /research litreview, /research compare

MCP prompts (via servers)

  • fastmcp-local: notes:capture, notes:summarize, plan:strategy, research:web, research:litreview, research:compare
  • database-tools: db:schema, db:optimize, db:migrate
  • dev-tools: dev:review, dev:architecture, dev:api, dev:docker, dev:testing
  • custom-tools: ai:prompt-engineer, api:changelog, brainstorm:ideas, cloud:deploy, dev:analyze, dev:refactor, docs:api, docs:readme, explore:codebase, explore:map, ops:runbook, perf:audit, qa:testplan, quality:review, refactor:plan, security:threatmodel

Paths and portability

  • All server commands use relative paths (e.g. servers/<name>/start-stdio.sh), resolved relative to .gemini/mcp at runtime.
  • Each server script cds into its own directory and creates/uses a local .venv there. No global installs required.
  • No hardcoded absolute paths in this repo. The only notable defaults are:
    • Filesystem server allowed roots use $HOME and $HOME/.gemini. If your client does not expand env vars in JSON, replace these with explicit paths.
    • notes:capture defaults to save at ~/.gemini/notes/inbox.md. Override with --save=PATH if desired.

Getting started

Prerequisites: Node.js/npm, Python 3.8+ with pip and venv.

git clone https://github.com/OWNER/gemini-cli-git-commands.git
cd gemini-cli-git-commands

# From the project root, run Gemini with your query/command
gemini /research web "latest trends in software architecture"
gemini /db design "blog app with users and posts"
gemini /notes capture "sync with team on Friday"

If a command references an optional server (e.g., fetch, postgres, sqlite) make sure your client has it configured or add it to .gemini/mcp/servers.json.

Development

  • Add new commands by creating .toml files under .gemini/commands/<category>/.
  • Add/modify local MCP servers under .gemini/mcp/servers/<name>/ and reference them in .gemini/mcp/servers.json.

License

MIT. See LICENSE.

Contributing

Please see CONTRIBUTING.md. A CODE_OF_CONDUCT.md applies to all interactions.

About

referencing the Gemini CLI blog for custom command

Resources

License

Code of conduct

Contributing

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published