Gemini CLI for agents: code review and big-context analysis
Delegate code reviews, plan reviews, and >200k-token analyses to Gemini 3 Pro via the Gemini CLI — with the yolo-mode safety rules so background runs never hang on approval prompts
- What
- Delegate code reviews, plan reviews, and >200k-token analyses to Gemini 3 Pro via the Gemini CLI — with the yolo-mode safety rules so background runs never hang on approval prompts
- Cost
- Free
- Needs
- the Gemini CLI installed (v0.16.0 or later for Gemini 3 support) and a Google API key saved in the secure vault — Gemini API usage is billed. The skill is a runbook the agent follows, not software to install.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @softaworks's skill for running the Gemini CLI from an agent: use when asked to activate Gemini for code review, plan review, or big-context (>200k tokens) processing. It carries a model table (gemini-3-pro-preview as the default flagship, gemini-3-flash for speed, 2.5 variants as legacy cost options) with a critical background-mode warning: never use --approval-mode default in non-interactive shells — it hangs forever on approval prompts; use yolo for automated runs or wrap with timeout, plus a troubleshooting guide for hung Gemini processes (detect via ps, kill, prevent). Covers command assembly (model, approval mode, -i interactive, --include-directories, --sandbox), common use cases (background code review, plan review, big-context analysis, interactive-only terminal review), follow-up session habits, and error handling (stop and report failures, ask permission before yolo on high-impact flags). Honest caveats: you need the Gemini CLI installed (v0.16.0+ for Gemini 3) and a Google API key — Gemini API usage is billed; note that yolo mode auto-approves ALL tool actions, so background reviews can execute anything the CLI can do — scope the prompt and directory tightly; and Gemini CLI sessions are one-shot, no resume — follow-ups start a new session. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: the Gemini CLI installed (v0.16.0 or later for Gemini 3 support) and a Google API key saved in the secure vault — Gemini API usage is billed. The skill is a runbook the agent follows, not software to install. Install "Gemini CLI for agents: code review and big-context analysis" for me. It gives my agent @softaworks's Gemini runbook: model selection (gemini-3-pro-preview default, flash for speed), approval-mode rules (yolo for background/automated, default only in interactive terminals — never the reverse, or the run hangs), command assembly, use-case recipes (code review, plan review, big-context analysis), follow-up habits, error handling, and the hung-process troubleshooting guide. MIT-licensed. Repository: https://github.com/softaworks/agent-toolkit/blob/main/dist/plugins/gemini/skills/gemini/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "gemini". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. install the Gemini CLI and confirm the API key is in the vault; scope background runs tightly — yolo mode auto-approves all tool actions). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.