gemini-reviewer
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Manual integration
- External API key
- Not required
- Operating systems
- Docker
- Runtime requirements
- Docker
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: gemini-reviewer
description: Use Google Gemini for parallel code reviews, complex task validation, and second opinions. Runs…
category: engineering
runtime: Docker
---
# gemini-reviewer output preview
## PART A: Task fit
- Use case: Use Google Gemini for parallel code reviews, complex task validation, and second opinions. Runs Gemini CLI non-interactively to provide alternative perspectives on code quality, implementation decisions, and technical solutions. Use when this capability is needed..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Execution Protocol / Context File Template / CONTEXT” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Use Google Gemini for parallel code reviews, complex task validation, and second opinions. Runs Gemini CLI non-interactively to provide alternative perspectives on code quality, implementation decisions, and technical solutions. Use when this capability is needed.”.
- **02** When the source has headings, the agent prioritizes “Execution Protocol / Context File Template / CONTEXT” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source mentions slash commands such as `/tmp`, `/code-review`, `/yolo`; use them first when your agent supports command triggers.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Validate with a small run
Start with a small task and check whether the result follows “Execution Protocol / Context File Template / CONTEXT”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: gemini-reviewer
description: Use Google Gemini for parallel code reviews, complex task validation, and second opinions. Runs…
category: engineering
source: tomevault-io/skills-registry
---
# gemini-reviewer
## When to use
- Use Google Gemini for parallel code reviews, complex task validation, and second opinions. Runs Gemini CLI non-interac…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Execution Protocol / Context File Template / CONTEXT” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "gemini-reviewer" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Execution Protocol / Context File Template / CONTEXT
rules -> SKILL.md triggers / order / output contract
runtime -> Docker | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Gemini Reviewer Skill
IMPORTANT: This skill executes automatically. When invoked, follow these steps precisely.
Execution Protocol
When this skill is invoked, you MUST:
Identify the review target from conversation context:
- Look for PR/MR numbers mentioned
- Look for commit hashes mentioned
- Look for code snippets or implementation plans
- Check recent tool calls (glab mr view, gh pr view, git diff, etc.)
Prepare comprehensive review context file:
- Include MR/PR title and description
- Include all code changes (diff)
- Include relevant file contents
- Include upstream issues or comments
- Include helper functions or related code
Execute Gemini review using Bash tool with read-only security:
gemini --approval-mode plan -o text -p "You are an expert code reviewer. Review this [MR/PR/code] and provide detailed feedback on correctness, security, performance, code quality, and testing. Be specific and reference line numbers or code sections." < /tmp/gemini_context.txtSECURITY NOTE:
--approval-mode plan: Read-only mode preventing all tool execution- Gemini can only analyze the provided context and return text feedback
- No file system modifications, git operations, or shell commands possible
- Note: Docker
--sandboxnot used due to enterprise UID compatibility issues
Return the complete Gemini output - do not summarize or filter
Context File Template
Create /tmp/gemini_context.txt with this structure:
Review [GitLab MR/GitHub PR/Commit] #[NUMBER]: "[TITLE]"
## CONTEXT
**Purpose:** [What this change does]
**Related Issues:** [Links to upstream issues, bugs, etc.]
**Rationale:** [Why this change is needed]
**CI Status:** [Pipeline/test results if available]
## CHANGES SUMMARY
[High-level summary of what files changed and why]
## DETAILED CODE CHANGES
### File: [filename]
```[language]
[Show diff with - and + for removed/added lines]File: [filename2]
[Show diff]HELPER FUNCTION CONTEXT
[Include any related helper functions or dependencies that aren't in the diff]
REVIEW FOCUS
Please review focusing on:
- Correctness: Logic errors, edge cases
- Security: Input validation, vulnerabilities
- Performance: Scalability, efficiency concerns
- Edge Cases: Null handling, error conditions
- Architecture: Design soundness, alternatives
- Code Quality: Readability, maintainability
- Testing: What tests should be added?
- Configuration: Impact of config changes
Provide specific, actionable feedback with line references.
## Example Execution
**Scenario:** /code-review command called with MR 44
Following the execution protocol above, here's a concrete example:
```bash
# Step 2: Prepare context file
cat > /tmp/gemini_context.txt << 'EOF'
Review GitLab Merge Request #44: "Tuning rag score thresholds"
## CONTEXT
[Full MR description, purpose, rationale]
## DETAILED CODE CHANGES
[Complete diff from glab mr diff]
## REVIEW FOCUS
[Specific areas to examine]
EOF
# Step 3: Execute Gemini in read-only plan mode
gemini --approval-mode plan -o text -p "You are an expert code reviewer. Review this merge request and provide detailed feedback on correctness, security, performance, and code quality. Be specific and reference line numbers." < /tmp/gemini_context.txtCritical Rules
- ALWAYS use
--approval-mode plan- Read-only mode preventing all tool execution - ALWAYS use
-pflag - Required for prompts when using stdin input - NEVER use
-y/YOLO mode - Auto-approves dangerous operations (rm, git reset, etc.) - ALWAYS use
-o text- Clean text output format - DO NOT use
--sandbox- Has compatibility issues with enterprise UID ranges (4212687 > 60000) - DO NOT summarize or filter Gemini's output - return it verbatim
- DO gather sufficient context - include diffs, descriptions, related code
- DO focus the prompt - tell Gemini what to look for
- DO use temporary files (
/tmp/gemini_context.txt) for large context
Troubleshooting
If Gemini is not installed:
- Report to user that Gemini CLI is not available
- Skip Gemini review and note it in the combined output
If Gemini returns an error:
- Include the error in the output
- Note that Gemini review failed but continue with other reviews
Integration with /code-review
This skill is automatically invoked by /code-review command alongside Claude's code-reviewer agent. Both run in parallel for comprehensive coverage.
Source: ccronca/dotfiles — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review