Collaborating with Gemini (Codex)

Use Gemini CLI as a collaborator while keeping Codex as the primary implementer.

This skill provides a lightweight bridge script that returns structured JSON and supports multi-turn sessions via SESSION_ID.

Core rules

• Gemini is a collaborator; you own the final result and must verify changes locally.
• Do not invoke gemini directly; always use the bridge script (scripts/gemini_bridge.py) so output/session handling stays consistent.
• Prefer file/line references over pasting snippets. Run the bridge with --cd set to the repo root (it sets the gemini process working directory). Use --cd "." only if your CWD is the repo root.
• For code changes, request Unified Diff Patch ONLY and forbid direct file modification.
• Always capture SESSION_ID and reuse it for follow-ups to keep the collaboration conversation-aware.
• Keep a short Collaboration State Capsule updated while this skill is active.
• Default timeout: when invoking via the Codex command runner, set timeout_ms to 600000 (10 minutes) unless a shorter/longer timeout is explicitly required.
• Optional: pass --sandbox to run Gemini in sandbox mode.

Quick start (shell-safe)

⚠️ If your prompt contains Markdown backticks (`like/this`), do not pass it directly via --PROMPT "..." (your shell may treat backticks as command substitution). Use a heredoc instead; see references/shell-quoting.md.