gemini-cli-execution

# Gemini CLI Execution

## 🚨 MANDATORY: Invoke gemini-cli-docs First

> **STOP - Before executing ANY Gemini CLI command:**
>
> 1. **INVOKE** `gemini-cli-docs` skill
> 2. **QUERY** for the specific CLI command syntax (e.g., "headless mode", "piping input")
> 3. **BASE** all execution patterns EXCLUSIVELY on official documentation loaded

## Overview

This skill provides the operational knowledge to execute the `gemini` binary effectively within scripts, sub-agents, and automation workflows. It focuses on **non-interactive** usage.

## Command Syntax (v0.18+)

**IMPORTANT**: Gemini CLI uses **positional prompts**, not subcommands.

```bash
# Correct syntax (positional prompt):
gemini "Your prompt here"

# With options:
gemini "Your prompt" --output-format json -m gemini-2.5-flash

# DEPRECATED (will be removed):
gemini -p "Your prompt"  # -p flag is deprecated

# WRONG (no 'query' subcommand exists):
gemini query "Your prompt"  # This does NOT work
```

## When to Use This Skill

**Keywords:** run gemini, execute gemini, gemini cli command, headless gemini, pipe to gemini, automated planning, gemini prompt, interactive shell

**Use this skill when:**

- Invoking Gemini CLI from an agent (e.g., `gemini-planner`)
- Running one-off queries: `gemini "prompt"`
- Piping context: `cat file.js | gemini "refactor this"`
- Using **Interactive Shell** for tools like `vim` or `top`
- Scripting complex workflows involving Gemini

## Execution Patterns

### 1. Single Shot Query (Non-Interactive)

Use positional prompt for direct queries:

```bash
gemini "Create a plan for a React app"

# With JSON output for parsing:
gemini "Create a plan for a React app" --output-format json
```

### 2. Piping Context

Pass file content or logs via stdin:

```bash
cat logs.txt | gemini "Analyze these error logs"

# With model selection:
cat src/*.ts | gemini "Review this code" -m gemini-2.5-flash
```

### 3. JSON Output for Automation

Always use `--output-format json` for scripting:

```bash
re