Gemini CLI Integration

Gemini CLI is the large-context handoff in this repository. Use it when the task is about the shape of a system, a broad slice of a repo, or a mixed text dataset that should be synthesized in one pass.

When to Use Gemini

Ideal Cases

Not Ideal

Host Entry Points

Claude Code

Use the slash command:

/cc-gemini-plugin:gemini <task>
/cc-gemini-plugin:gemini --dirs src,docs <task>
/cc-gemini-plugin:gemini --files "schemas/**/*.json" <task>

Claude can also spawn gemini-agent when the task obviously benefits from a large-context pass.

Codex

• Mention the skill explicitly with $gemini-integration.
• Or ask Codex to use the Gemini integration for a large analysis task.

Codex reads this skill definition directly when the repository is installed as a user-level skill.

Shared Runtime Contract

Always prefer the shared bridge script over hand-written gemini commands:

node scripts/gemini-bridge.js [options] <task>

The bridge owns:

• argument parsing
• directory and file ingestion
• structured prompt assembly
• Gemini CLI invocation

Use:

• --dirs <path,...> for broad module trees
• --files <glob,...> for targeted globs and mixed data formats
• --model <name> only when the caller explicitly wants a model override
• --format json only when structured output is required
• --print-command when you need to inspect the resolved Gemini command

Good Patterns

Architecture

node scripts/gemini-bridge.js --dirs src,docs \
  "Explain the architecture and cite the key files."

Refactor impact

node scripts/gemini-bridge.js --dirs src \
  "Analyze the impact of refactoring the auth module. Include affected files and migration steps."

Structured data

node scripts/gemini-bridge.js --files "schemas/**/*.json,data/**/*.csv" \
  "Summarize the data contracts and identify breaking changes."

Troubleshooting