alexei-led/using-gemini

<!-- generated by scripts/build/generate-skills.py — edits to this file will be overwritten by `make build`. Edit the canonical SKILL.md (or add a SKILL.codex.md / SKILL.pi.md sidecar to diverge). --> <!-- Platform guidance for non-Claude models (Codex CLI, Gemini CLI) --> <!-- Persistence: Keep going until the task is fully resolved. Do not stop at the first obstacle. --> <!-- Tool use: Use available tools to verify — do not guess at file contents, paths, or command output. --> <!-- Planning: Reflect between steps. Decompose complex problems into logical sub-steps before acting. --> <!-- Reliability: Assess risk before irreversible actions. Ask for clarification on ambiguity. --> <!-- Completeness: Generate complete responses without truncating. Review your output against the original constraints. -->

Gemini CLI Integration

Consult Google Gemini via CLI for second opinions, brainstorming, or web search.

Critical Workflow Rules

• When the user asks to "ask Gemini" or "gemini search", run the gemini CLI when available; do not only suggest a command.
• Scope what is sent. Do not send secrets, credentials, private code, or whole repos unless the user explicitly approves and the context is necessary.
• For second opinions, compare Gemini output against local code, requirements, ADRs, or other existing evidence. Gemini is critique, not authority.
• For web/search use, ask Gemini for recent examples with source URLs, then cross-check against official docs or local project constraints before recommending changes.
• Final synthesis must separate: agreements, disagreements, unsupported claims, and actionable next steps.
• If Gemini is unavailable, report the exact blocker and provide the command that would be run.

Usage

Run Gemini in non-interactive (headless) mode:

# General query
gemini -p "your question here"

# With specific model
gemini -m gemini-2.5-pro -p "your question"

# Pipe context into Gemini
cat file.go | gemini -p "review this code for issues"

When to Use

• Second opinion: Get Gemini's perspective on architecture, design, or code
• Web search: Ask Gemini to search for current information
• Brainstorming: Generate alternative approaches or ideas
• Media analysis: Describe images or analyze file content

Workflow

1. Gather only the relevant context from the codebase if needed
2. Formulate a clear, scoped prompt
3. Run gemini -p "prompt" for non-interactive response
4. Verify or cross-check Gemini's claims against local evidence or official sources
5. Summarize agreements, disagreements, unsupported claims, and actionable next steps

Tips

• Keep prompts focused and specific for best results
• Pipe file content directly when asking about specific code
• Use -m flag to select a specific Gemini model if needed