Use when the user asks to run Gemini CLI for code review, plan review, or big context (>200k) processing. Ideal for comprehensive analysis requiring large context windows. Uses Gemini 3 Pro by default for state-of-the-art reasoning and coding.
/plugin marketplace add iamladi/cautious-computing-machine--sdlc-plugin/plugin install sdlc@cautious-computing-machineThis skill inherits all available tools. When active, it can use any tool Claude has access to.
NEVER use --approval-mode default in background or non-interactive shells (like Claude Code tool calls). It will hang indefinitely waiting for approval prompts that cannot be provided.
For automated/background reviews:
--approval-mode yolo for fully automated executiontimeout 300 gemini ...--approval-mode default without interactive terminalSymptoms of hung Gemini:
Fix hung process:
# Check if hung
ps aux | grep gemini | grep -v grep
# Kill if necessary
pkill -9 -f "gemini.*gemini-3-pro-preview"
Ask the user (via AskUserQuestion) which model to use in a single prompt. Available models:
gemini-3-pro-preview ⭐ (flagship model, best for coding & complex reasoning, 35% better at software engineering than 2.5 Pro)gemini-3-flash (sub-second latency, distilled from 3 Pro, best for speed-critical tasks)gemini-2.5-pro (legacy option, strong all-around performance)gemini-2.5-flash (legacy option, cost-efficient with thinking capabilities)gemini-2.5-flash-lite (legacy option, fastest processing)Select the approval mode based on the task:
default: Prompt for approval (⚠️ ONLY for interactive terminal sessions)auto_edit: Auto-approve edit tools only (for code reviews with suggestions)yolo: Auto-approve all tools (✅ REQUIRED for background/automated tasks)Assemble the command with appropriate options:
-m, --model <MODEL> - Model selection--approval-mode <default|auto_edit|yolo> - Control tool approval-y, --yolo - Alternative to --approval-mode yolo-i, --prompt-interactive "prompt" - Execute prompt and continue interactively--include-directories <DIR> - Additional directories to include in workspace-s, --sandbox - Run in sandbox mode for isolationFor background/automated tasks, ALWAYS use --approval-mode yolo or add timeout wrapper. NEVER use default in non-interactive shells.
Run the command and capture the output. For background/automated mode:
# Recommended: Use yolo for background tasks
gemini -m gemini-3-pro-preview --approval-mode yolo "Review this codebase for security issues"
# Or with timeout (5 min limit)
timeout 300 gemini -m gemini-3-pro-preview --approval-mode yolo "Review this codebase"
For interactive sessions with an initial prompt:
gemini -m gemini-3-pro-preview -i "Review the authentication system" --approval-mode auto_edit
After Gemini completes, inform the user: "The Gemini analysis is complete. You can start a new Gemini session for follow-up analysis or continue exploring the findings."
| Use case | Approval mode | Key flags |
|---|---|---|
| Background code review | yolo ✅ | -m gemini-3-pro-preview --approval-mode yolo |
| Background analysis | yolo ✅ | -m gemini-3-pro-preview --approval-mode yolo |
| Background with timeout | yolo ✅ | timeout 300 gemini -m gemini-3-pro-preview --approval-mode yolo |
| Interactive code review | default | -m gemini-3-pro-preview --approval-mode default (interactive terminal only) |
| Code review with auto-edits | auto_edit | -m gemini-3-pro-preview --approval-mode auto_edit |
| Automated refactoring | yolo | -m gemini-3-pro-preview --approval-mode yolo |
| Speed-critical background | yolo ✅ | -m gemini-3-flash --approval-mode yolo |
| Cost-optimized background | yolo ✅ | -m gemini-2.5-flash --approval-mode yolo |
| Multi-directory analysis | yolo (if background) | --include-directories <DIR1> --include-directories <DIR2> |
| Interactive with prompt | auto_edit or default | -i "prompt" --approval-mode <mode> |
| Model | Best for | Context window | Key features |
|---|---|---|---|
gemini-3-pro-preview ⭐ | Flagship model: Complex reasoning, coding, agentic tasks | 1M input / 64k output | Vibe coding, 76.2% SWE-bench, $2-4/M input |
gemini-3-flash | Sub-second latency, speed-critical applications | 1M input / 64k output | Distilled from 3 Pro, TPU-optimized |
gemini-2.5-pro | Legacy: Strong all-around performance | 1M input / 65k output | Thinking mode, mature stability |
gemini-2.5-flash | Legacy: Cost-efficient, high-volume tasks | 1M input / 65k output | Best price ($0.15/M), thinking mode |
gemini-2.5-flash-lite | Legacy: Fastest processing, high throughput | 1M input / 65k output | Maximum speed, minimal latency |
Gemini 3 Advantages: 35% higher accuracy in software engineering, state-of-the-art on SWE-bench (76.2%), GPQA Diamond (91.9%), and WebDev Arena (1487 Elo). Knowledge cutoff: January 2025.
Coming Soon: gemini-3-deep-think for ultra-complex reasoning with enhanced thinking capabilities.
# For background execution (Claude Code, CI/CD, etc.)
gemini -m gemini-3-pro-preview --approval-mode yolo \
"Perform a comprehensive code review focusing on:
1. Security vulnerabilities
2. Performance issues
3. Code quality and maintainability
4. Best practices violations"
# With timeout safety (5 minutes)
timeout 300 gemini -m gemini-3-pro-preview --approval-mode yolo \
"Perform a comprehensive code review..."
# For background execution
gemini -m gemini-3-pro-preview --approval-mode yolo \
"Review this architectural plan for:
1. Scalability concerns
2. Missing components
3. Integration challenges
4. Alternative approaches"
# For background execution
gemini -m gemini-3-pro-preview --approval-mode yolo \
"Analyze the entire codebase to understand:
1. Overall architecture
2. Key patterns and conventions
3. Potential technical debt
4. Refactoring opportunities"
# ONLY use default mode in interactive terminal
gemini -m gemini-3-pro-preview --approval-mode default \
"Review the authentication flow for security issues"
AskUserQuestion after each Gemini command to confirm next steps or gather clarifications.gemini --version or a Gemini command exits non-zero.--approval-mode yolo, -y, --sandbox), ask the user for permission using AskUserQuestion unless already granted.AskUserQuestion.# Check for hung processes
ps aux | grep -E "gemini.*gemini-3" | grep -v grep
# Look for these symptoms:
# - Process running 20+ minutes
# - CPU usage at 0%
# - Process state 'S' (sleeping)
# - No network connections
# Get detailed process info
ps -o pid,etime,pcpu,stat,command -p <PID>
# Check network activity
lsof -p <PID> 2>/dev/null | grep -E "(TCP|ESTABLISHED)" | wc -l
# If result is 0, process is hung
# Kill hung Gemini processes
pkill -9 -f "gemini.*gemini-3-pro-preview"
# Or kill specific PID
kill -9 <PID>
# Verify cleanup
ps aux | grep gemini | grep -v grep
--approval-mode yolo for background/automated taskstimeout 300 gemini ...--approval-mode default in non-interactive shellsps to ensure process completesgemini-3-pro-preview for complex reasoning, coding tasks, and maximum analysis quality (recommended default)gemini-3-flash for speed-critical tasks requiring sub-second response timesgemini-2.5-flash for cost-optimized high-volume processingRequires Gemini CLI v0.16.0 or later for Gemini 3 model support. Check version: gemini --version
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.