geminilisted

Use Gemini as a third external reviewer alongside two other vendors: diff review with an APPROVE or REQUEST_CHANGES verdict, and QA-breaker duty in the post-build test ritual. Headless over REST with a CLI fallback, and verdicts go to a shared usage journal. Triggers: "/gemini review", "gemini opinion on this diff".
tonydzi/second-brain-starter-kit · ★ 6 · Code & Development · score 78

Install: claude install-skill tonydzi/second-brain-starter-kit

# gemini — the third vendor in the "second pair of eyes" Its siblings: **Codex** (`secondop.py` / `codex_review.py`, the default) and **Grok** (`grok_review.py`, a CLI on the hub). Gemini is the third independent vendor: it rescues the verdict when Codex has burned through its quota, and as a hetero-pair it breaks what the other two never saw. ## When I call it - In **/tt Step 2.5**, rail 3: Codex unavailable/quota-blocked · a contested COUNTER · a safety-critical artifact (call two or three of them) · the operator says "ask Gemini". - Diff review alongside `cc_review.py` / `codex_review.py` / `grok_review.py`. - A third voice on architecture/plan review when Claude and Codex disagree. ## How (headless, no browser) The breaker for /tt (the verdict is logged into `secondop` automatically, no manual `log-ext` needed): ``` python "%USERPROFILE%\.claude\scripts\cc-review\gemini_review.py" break --task <task-id> --context "<what we built + what has already been checked>" ``` Diff review: ``` python "%USERPROFILE%\.claude\scripts\cc-review\gemini_review.py" review --repo "<path to the repo>" ``` Is the rail alive (before the ritual leans on it): ``` python "%USERPROFILE%\.claude\scripts\cc-review\gemini_review.py" doctor ``` Flags: `--range "HEAD~1 HEAD"` · `--diff <patch>` · `--task <task.md>` (what was asked for) · `--model <model>` · `--engine cli|rest` · `--timeout S` · `--no-log` (break without writing to usage.jsonl). ## How to read the answer - `break`: the first line