collaborating-with-gemini — Claude Code skill: setup guide
collaborating-with-gemini connects Gemini CLI as a second opinion for diff inspection, bug analysis, and prototyping via a Python bridge.
no license ★ 475 updated 2026-10-13
npx skills add cnfjlhj/ai-collab-playbook --skill collaborating-with-gemini -a claude-codeWhat collaborating-with-gemini does
This skill connects your workspace agent to Gemini CLI using scripts/gemini_bridge.py. The bridge wrapper emits structured JSON and maintains multi-turn dialogs by tracking SESSION_ID across subsequent calls. That lets you ask follow-up questions without restarting conversation context from scratch.
Prompts reference file paths and line ranges instead of dumping raw code blocks into terminal arguments. The bridge takes --cd pointing to the repository root. For suggested edits, the instructions demand output strictly as a Unified Diff Patch and prohibit touching source files directly. Optional arguments include --model, --sandbox, and --return-all-messages.
Execution relies on Python 3 and a functional Gemini CLI installation. When sharing UI snapshots, store PNG files in .codex_uploads/ rather than the system temp directory, because Gemini refuses to inspect files outside the active workspace root.
What it helps with
- gather a second perspective on tricky edge cases and logic bugs
- review proposed patch risks before committing code changes
- continue multi-turn troubleshooting conversations via SESSION_ID
- evaluate UI readability and design alternatives safely
Example prompts for the agent
- Run gemini_bridge.py to ask Gemini CLI for edge cases in src/auth.py around login()
- Continue the Gemini session with SESSION_ID and request a fix strictly as a Unified Diff Patch
- Pass the image inside .codex_uploads/ to Gemini CLI to review the updated layout
How to install collaborating-with-gemini
1Skills CLI (Vercel)
npx skills add cnfjlhj/ai-collab-playbook --skill collaborating-with-gemini -a claude-code2Manually: put the files in place
~/.claude/skills/collaborating-with-gemini/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/collaborating-with-gemini/
1Skills CLI (Vercel)
npx skills add cnfjlhj/ai-collab-playbook --skill collaborating-with-gemini -a codex2Manually: put the files in place
.agents/skills/collaborating-with-gemini/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add cnfjlhj/ai-collab-playbook --skill collaborating-with-gemini -a cursor2Manually: put the files in place
.cursor/skills/collaborating-with-gemini/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install cnfjlhj/ai-collab-playbook skills/full/collaborating-with-gemini2Manually: put the files in place
.github/skills/collaborating-with-gemini/SKILL.md1Skills CLI (Vercel)
npx skills add cnfjlhj/ai-collab-playbook --skill collaborating-with-gemini -a gemini-cli2Platform CLI
gemini skills install https://github.com/cnfjlhj/ai-collab-playbook --path skills/full/collaborating-with-geminiManually: put the files in place
.devin/skills/collaborating-with-gemini/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about collaborating-with-gemini
How to install collaborating-with-gemini in Claude Code?
Run npx skills add cnfjlhj/ai-collab-playbook --skill collaborating-with-gemini -a claude-code in your terminal.
What does collaborating-with-gemini do?
It routes debugging, code review, and prototyping prompts to Gemini CLI through a bridge script that outputs JSON with session support.
Can Gemini modify files in the project directly?
No, the prompt constraints require Gemini to return only unified diff patches so you can inspect and apply edits locally.