git:20260928.cf9620c to git:20261002.162238f

2 added, 36 removed. Audit A to A.

---

name: gemini-review

- description: Get a second opinion from Gemini on your current code changes. Analyzes staged/unstaged diffs and returns prioritized findings. Use when user asks to "review with Gemini", "Gemini code review", or "ask Gemini to check my code".

+ description: Earlier name of the ask-llm-gemini-review skill; use when the user invokes /gemini-review.

---

-

- ## Portable contract

- Gather the relevant staged, unstaged, and untracked code changes; build a bounded context brief; request a Gemini review; verify each reported finding against source; and return only prioritized, source-supported findings. Preserve the canonical `gemini-3.1-pro-preview` → `gemini-3.8-flash` quota fallback, timeout, and explicit failure disclosure.

-

- ## Host adapters

- ### Pi adapter

- Call the native `ask-gemini` tool and apply only the `Portable contract` section of `../../agents/gemini-reviewer.md`; ignore that file's frontmatter and Claude Code adapter.

-

- ### Claude Code adapter

- The existing detailed workflow below is the Claude Code adapter. Its Agent, MCP, hook, `CLAUDE_PLUGIN_ROOT`, and `AskUserQuestion` mechanics apply only on Claude Code; they do not override the Pi adapter above.

- # Gemini Code Review

- Review current code changes by delegating to the `gemini-reviewer` agent.

- ## Instructions

- 1. Gather the diff to review:

- - Run `git diff` to get unstaged changes

- - Run `git diff --cached` to get staged changes

- - Combine both into a single diff

- 2. If the diff is empty, inform the user there are no changes to review.

- 3. Launch the `gemini-reviewer` agent with the diff content. The agent handles the Gemini prompt structure and output formatting.

-

+ `gemini-review` is the earlier name of `ask-llm-gemini-review`. Load `../ask-llm-gemini-review/SKILL.md` and follow it exactly, passing along any arguments the user gave `/gemini-review`.