### Manual GitHub Actions Workflow Setup

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/integrations/github.mdx

Manually create a GitHub Actions workflow file (`.github/workflows/roborev.yml`) to integrate roborev. This example shows how to check out code, install roborev, and run a CI review with a specified agent and environment variables.

```yaml
name: roborev
on:
  pull_request:
    types: [opened, synchronize]

permissions:
  contents: read
  pull-requests: write

jobs:
  review:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0

      - name: Install roborev
        run: |
          curl -fsSL https://roborev.dev/install.sh | bash
          echo "$HOME/.roborev/bin" >> "$GITHUB_PATH"

      - name: Run review
        env:
          ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
        run: roborev ci review --comment --agent claude-code
```

--------------------------------

### Clone and Install Roborev

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/development.mdx

Clone the repository, navigate to the directory, and run tests. Use `make install` for a versioned installation or `go install` for quick iteration.

```bash
git clone https://github.com/roborev-dev/roborev
cd roborev
go test ./...
make install    # Installs with version info (e.g., v0.7.0-5-gabcdef)
```

--------------------------------

### Install with Version Info

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/development.mdx

Use `make install` to build and install the project with version information embedded. This is recommended for official releases.

```bash
make install
```

--------------------------------

### Initialize roborev in a repository

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/quickstart.mdx

Run this command in your project's root directory to set up roborev. It installs a post-commit hook and starts the roborev daemon, enabling automatic AI code reviews for every commit.

```bash
cd your-repo
roborev init
```

--------------------------------

### Install Roborev Binary

Source: https://context7.com/roborev-dev/roborev-docs/llms.txt

Install the roborev binary using various methods including a script, Homebrew, or Go. Verify the installation with the 'version' command.

```bash
# macOS/Linux via install script
curl -fsSL https://roborev.dev/install.sh | sh
```

```bash
# Homebrew
brew install roborev-dev/tap/roborev
```

```bash
# Go
go install github.com/roborev-dev/roborev@latest
```

```bash
# Verify
roborev version
```

--------------------------------

### Roborev Summary Command Examples

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/commands.mdx

Use the `summary` command to get statistics about code reviews. Options allow filtering by time, branch, repository, and output format.

```bash
roborev summary                     # Last 7 days, current repo
```

```bash
roborev summary --all               # Last 7 days, all repos
```

```bash
roborev summary --since 30d         # Last 30 days
```

```bash
roborev summary --branch main       # Filter by branch
```

```bash
roborev summary --repo /path/to/repo
```

```bash
roborev summary --json              # Structured output for scripting
```

--------------------------------

### GitHub Actions Workflow Example

Source: https://context7.com/roborev-dev/roborev-docs/llms.txt

This is an example of a GitHub Actions workflow file generated by `roborev init gh-action`. It includes steps to install Roborev and run a review using specified agents and secrets.

```yaml
# .github/workflows/roborev.yml (generated by roborev init gh-action)
name: roborev
on:
  pull_request:
    types: [opened, synchronize]
jobs:
  review:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      pull-requests: write
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0
      - name: Install roborev
        run: curl -fsSL https://roborev.dev/install.sh | sh
      - name: Review PR
        env:
          ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        run: roborev ci review --agent claude-code --comment
```

--------------------------------

### Quick Install via PowerShell (Windows)

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/installation.mdx

Execute this PowerShell command to install the latest roborev release binary on Windows. It installs to `%USERPROFILE%\.roborev\bin` and adds it to your PATH. Both x64 and ARM64 are supported.

```powershell
powershell -ExecutionPolicy ByPass -c "irm https://roborev.io/install.ps1 | iex"
```

--------------------------------

### Global Configuration Example (~/.roborev/config.toml)

Source: https://context7.com/roborev-dev/roborev-docs/llms.txt

Example TOML file for global Roborev settings, including default agents, server addresses, worker counts, and CI/sync configurations.

```toml
# ~/.roborev/config.toml

default_agent = "codex"
default_backup_agent = "claude-code"
default_model = "gpt-5.2-codex"
server_addr = "127.0.0.1:7373"   # or "unix://" for Unix domain socket
max_workers = 4
job_timeout = "10m"
review_context_count = 3
auto_close_passing_reviews = false
review_min_severity = "low"
hide_closed_by_default = false
auto_filter_repo = true
auto_filter_branch = false
mouse_enabled = true
default_max_prompt_size = 200000

# Agent command overrides (if not on default PATH)
claude_code_cmd = "/usr/local/bin/claude"
codex_cmd = "codex"

# Exclude lockfiles globally
exclude_patterns = ["package-lock.json", "yarn.lock", "go.sum", "Cargo.lock"]

# Hooks
[[hooks]]
event = "review.failed"
command = "notify-send 'roborev' 'Review FAILED: {repo_name} ({sha})'"

[[hooks]]
event = "review.completed"
type = "webhook"
url = "https://hooks.example.com/roborev"

# GitHub CI poller
[ci]
enabled = true
poll_interval = "5m"
repos = ["myorg/api-service", "myorg/frontend-*"]
exclude_repos = ["myorg/frontend-archived"]
agents = ["codex", "claude-code"]
review_types = ["security", "default"]
min_severity = "medium"
upsert_comments = true
github_app_id = 123456
github_app_private_key = "/home/user/.roborev/github-app.pem"
github_app_installations = { myorg = 789012 }

# PostgreSQL sync (multi-machine)
[sync]
enabled = true
postgres_url = "postgres://roborev:${ROBOREV_PG_PASS}@db.tailnet:5432/roborev"
interval = "1h"
machine_name = "laptop"

```

--------------------------------

### Install via Go

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/installation.mdx

Install roborev using the Go toolchain if you have Go installed. Ensure `$GOPATH/bin` is included in your system's PATH environment variable.

```bash
go install github.com/roborev-dev/roborev/cmd/roborev@latest
```

```bash
export PATH="$PATH:$(go env GOPATH)/bin"
```

--------------------------------

### Tap and Install via Homebrew (macOS/Linux)

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/installation.mdx

First tap the roborev-dev repository, then install roborev using Homebrew. This is an alternative method for installing via Homebrew.

```bash
brew tap roborev-dev/tap
brew install roborev
```

--------------------------------

### Per-Repository Configuration Example (.roborev.toml)

Source: https://context7.com/roborev-dev/roborev-docs/llms.txt

Example TOML file for configuring Roborev behavior on a per-repository basis, including agent settings, review guidelines, and exclusions.

```toml
# .roborev.toml — place in repository root

agent = "codex"
display_name = "My API Service"

# Review guidelines injected into every review prompt
review_guidelines = """
This is a REST API service. Focus on:
- Input validation and sanitization
- SQL injection and XSS risks
- Missing auth checks on endpoints
- Pagination on list endpoints
"""

# Branch and commit exclusions
excluded_branches = ["dependabot/*", "renovate/*"]
excluded_commit_patterns = ["^chore:", "^docs:", "WIP"]

# Exclude generated/vendor files from diffs
exclude_patterns = ["*.pb.go", "vendor/**", "**/*.min.js"]

# Automatically close reviews that pass with no findings
auto_close_passing_reviews = true

# Minimum severity to report (low, medium, high, critical)
review_min_severity = "medium"
fix_min_severity = "medium"

# Branch review on every commit (instead of per-commit)
post_commit_review = "branch"

# Per-workflow agent and model overrides
review_agent_thorough = "claude-code"
review_model_thorough = "claude-opus-4-5"
fix_agent = "codex"
backup_agent = "gemini"

# Security and design review agents
security_agent = "claude-code"
design_agent = "codex"

```

--------------------------------

### Initialize Repository with Roborev

Source: https://context7.com/roborev-dev/roborev-docs/llms.txt

Initialize roborev in the current repository to set up the daemon and install the Git post-commit hook. Supports auto-detection or specification of the AI agent, and can be run without starting the daemon.

```bash
# Initialize current repo with auto-detected agent
roborev init
```

```bash
# Initialize with a specific agent
roborev init --agent codex
```

```bash
# Initialize without starting the daemon
roborev init --no-daemon
```

```bash
# After init, the post-commit hook fires automatically on every commit:
git commit -m "Add auth validation"
# → roborev enqueues a background review immediately
```

--------------------------------

### Build from Source for Development

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/installation.mdx

Use `go install ./cmd/...` for quick iteration during development when building from source.

```bash
go install ./cmd/...
```

--------------------------------

### Install via Homebrew (macOS/Linux)

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/installation.mdx

Install roborev using Homebrew. This command directly installs the package from the roborev-dev tap.

```bash
brew install roborev-dev/tap/roborev
```

--------------------------------

### Verify Installation

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/installation.mdx

Check if roborev has been installed correctly by running the `version` command.

```bash
roborev version
```

--------------------------------

### Install roborev with Go

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/quickstart.mdx

Install the roborev CLI tool using the Go package manager. Ensure your $GOPATH/bin directory is included in your system's PATH environment variable.

```bash
go install github.com/roborev-dev/roborev/cmd/roborev@latest
```

--------------------------------

### GitHub App Configuration - Multiple Installations

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/integrations/github.mdx

Configure the GitHub App to use multiple installation IDs, allowing integration with different organizations or user accounts. Each installation ID should be mapped to its corresponding owner.

```toml
[ci]
enabled = true
poll_interval = "5m"
repos = ["wesm/my-project", "roborev-dev/core", "roborev-dev/docs"]
review_types = ["security"]
agents = ["codex"]

github_app_id = 123456
github_app_private_key = "~/.roborev/roborev.pem"

# Each org/user has its own app installation
[ci.github_app_installations]
wesm = 111111
roborev-dev = 222222
```

--------------------------------

### Install roborev CLI

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/index.mdx

Installs the roborev command-line interface using curl. This is the recommended installation method for Linux and macOS.

```bash
curl -fsSL https://roborev.io/install.sh | bash
```

--------------------------------

### Start a New Roborev Review

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/integrations/claudechic.mdx

Initiate a new roborev review using the /reviewer command, optionally providing context.

```bash
/reviewer [context]
```

--------------------------------

### Install and Verify gh CLI

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/integrations/github.mdx

Install the GitHub CLI and verify its installation. This is required for Roborev to interact with GitHub.

```bash
# Install: https://cli.github.com/
gh --version   # verify it's installed
```

--------------------------------

### Example Comments for Code Reviews

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/guides/responding-to-reviews.mdx

These examples demonstrate how to provide context, explanations, or acknowledgments within code review comments. Effective comments help train AI agents and reduce false positives.

```text
The singleton pattern here is intentional for the connection pool.
Thread safety is handled by the underlying driver.
```

```text
This is generated code from protobuf - we don't modify it directly.
Please ignore style issues in *.pb.go files.
```

```text
Good catch on the race condition! I'll add a mutex in the next commit.
```

--------------------------------

### Protocol and Examples

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/integrations/tui.mdx

Details on the JSON protocol used for communication and practical examples of its usage.

```APIDOC
## Protocol

Requests are sent as single JSON lines. Responses include an `ok` field, and optionally `error` or `data` fields.

### Request Format
```json
{"command": "<command_name>", "params": {<parameters>}}
```

### Response Format
```json
{"ok": <boolean>, "error": "<error_message>", "data": <data_object>}
```

### Example: Querying State
1. Find the socket path from runtime metadata:
   ```bash
   SOCKET=$(python3 -c "import json,glob; f=glob.glob('$HOME/.roborev/tui.*.json')[0]; print(json.load(open(f))['socket_path'])")
   ```
2. Send a `get-state` command:
   ```bash
   echo '{"command":"get-state"}' | nc -U "$SOCKET"
   ```

### Example: Setting Filter
1. Find the socket path (as above).
2. Send a `set-filter` command:
   ```bash
   echo '{"command":"set-filter","params":{"repo":"myproject"}}' | nc -U "$SOCKET"
   ```
```

--------------------------------

### Install Roborev Skills

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/guides/agent-skills.mdx

Run this command to install the necessary slash commands for your AI agent to interact with Roborev.

```bash
roborev skills install
```

--------------------------------

### Install and Manage Git Hooks

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/commands.mdx

Install, uninstall, or force reinstall the post-commit Git hook. Use `--force` to overwrite an existing hook.

```bash
roborev post-commit              # Hook entry point (called by git hook)
roborev install-hook             # Install post-commit hook
roborev install-hook --force     # Overwrite existing hook with a fresh one
roborev uninstall-hook           # Remove hook
```

--------------------------------

### Build from Source

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/installation.mdx

Clone the roborev repository and build the project from source using `make install`. This method embeds version information into the binary.

```bash
git clone https://github.com/roborev-dev/roborev
cd roborev
make install
```

--------------------------------

### List Available ACP Wrappers

Source: https://context7.com/roborev-dev/roborev-docs/llms.txt

Discover and list the available ACP-compatible agent wrappers, typically installed via npm.

```bash
# Available ACP wrappers (npm)
npx @zed-industries/codex-acp          # Codex via ACP
npx @zed-industries/claude-agent-acp   # Claude via ACP
gemini --experimental-acp              # Gemini via ACP
```

--------------------------------

### Verify ACP Setup

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/advanced/acp.mdx

Confirm the configured ACP command is on your PATH and test end-to-end communication by running a review.

```bash
which codex-acp          # or your configured command
roborev review HEAD
```

--------------------------------

### Install Claude Chic

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/integrations/claudechic.mdx

Install Claude Chic using uv or pip. Ensure roborev and Claude Code are in your PATH.

```bash
uv tool install claudechic   # recommended
pip install claudechic        # alternative
```

--------------------------------

### CI Pipeline Example with --wait

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/guides/reviewing-code.mdx

This example shows how to use `roborev review --branch --wait --quiet` within a CI pipeline to gate merges on review outcomes. If the review finds issues (non-zero exit code), the script echoes an error and exits.

```bash
# CI example
if ! roborev review --branch --wait --quiet; then
    echo "Reviews found issues"
    exit 1
fi
```

--------------------------------

### Start Roborev Daemon

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/integrations/github.mdx

Start the Roborev daemon in either background or foreground mode to begin processing CI tasks. Verify that the GitHub App authentication is enabled by checking the log output.

```bash
roborev daemon start        # background mode
roborev daemon run          # or foreground mode to watch logs
```

--------------------------------

### Configure Multiple GitHub App Installations

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/integrations/github.mdx

Map repository owners to specific GitHub App installation IDs when your repos span multiple organizations. This allows Roborev to use the correct installation for each. A fallback installation ID can be provided for owners not explicitly listed.

```toml
[ci]
enabled = true
repos = ["wesm/my-project", "roborev-dev/core"]

github_app_id = 123456
github_app_private_key = "~/.roborev/roborev.pem"

[ci.github_app_installations]
wesm = 111111
roborev-dev = 222222
```

```toml
[ci]
github_app_id = 123456
github_app_private_key = "~/.roborev/roborev.pem"
github_app_installation_id = 111111   # fallback for unlisted owners

[ci.github_app_installations]
roborev-dev = 222222                  # this org uses a different installation
```

--------------------------------

### Install ACP Wrapper Package

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/advanced/acp.mdx

Install the ACP wrapper package using npm if the command is not found.

```bash
npm install -g @zed-industries/codex-acp
```

--------------------------------

### Configure Max Prompt Size Per Repository

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/guides/assisted-refactoring.mdx

Example of setting the `max_prompt_size` in a `.roborev.toml` file for repository-specific large file handling configuration.

```toml
max_prompt_size = 204800
```

--------------------------------

### Configure GitHub App Authentication

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/integrations/github.mdx

Set up your GitHub App ID, private key path, and installation ID for authentication. The private key can be a file path, environment variable, or inline PEM content. Prefer file paths or environment variables to avoid committing keys.

```toml
github_app_id = 123456
github_app_private_key = "~/.roborev/roborev.pem"
github_app_installation_id = 12345678
```

--------------------------------

### Linux Systemd Configuration for Roborev Daemon

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/configuration.mdx

Enable and start the Roborev user-level service on Linux using systemd. This command enables the service to start automatically on boot.

```bash
systemctl --user enable --now roborev
```

--------------------------------

### Manage Roborev Configuration

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/commands.mdx

Get, set, and list configuration values. Specify `--global` or `--local` to target specific configuration files. Use `--show-origin` to see where each setting is defined.

```bash
roborev config get <key>             # Get value (merged: local then global)
roborev config get <key> --global    # Get from global config only
roborev config get <key> --local     # Get from repo config only

roborev config set <key> <value>     # Set in repo config (default)
roborev config set <key> <value> --global  # Set in global config

roborev config list                  # List merged config
roborev config list --show-origin    # Show where each value comes from
```

--------------------------------

### Global Hooks for All Repositories

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/guides/hooks.mdx

Define global hooks in '~/.roborev/config.toml' that apply to all repositories. This example shows logging for both completed and failed reviews.

```toml
# ~/.roborev/config.toml -- fires for all repos
[[hooks]]
event = "review.completed"
command = "echo {repo_name} {sha} {verdict} >> ~/roborev-events.log"

[[hooks]]
event = "review.failed"
command = "echo {repo_name} {sha} {error} >> ~/roborev-events.log"
```

--------------------------------

### Install and Manage Roborev Agent Skills

Source: https://context7.com/roborev-dev/roborev-docs/llms.txt

Commands to install, update, and check the status of bundled skills for coding agents. These skills allow agents to invoke Roborev directly from their sessions.

```bash
# Install skills for all detected agents
roborev skills install
```

```bash
# Update installed skills
roborev skills update
```

```bash
# Check installation status per agent
roborev skills
# Output:
#   claude-code  roborev-review          installed  (v0.54)
#   claude-code  roborev-fix             installed  (v0.54)
#   codex        roborev-review          installed  (v0.54)
#   codex        roborev-fix             outdated   (v0.50 → v0.54)
```

--------------------------------

### Stream Output Example

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/guides/assisted-refactoring.mdx

Shows the compact progress lines generated by `roborev fix` or `analyze --fix` when running an agent. Output includes tool calls with gutter prefixes.

```text
│ Read   internal/gmail/ratelimit_test.go
│ Edit   internal/gmail/ratelimit_test.go
│ Bash   go test ./internal/gmail/ -run TestRateLimiter
│ Edit   internal/gmail/ratelimit_test.go
│ Grep   TODO  internal/ 
```

--------------------------------

### Configure Max Prompt Size in TOML

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/guides/assisted-refactoring.mdx

Example of setting the `default_max_prompt_size` in `config.toml` to manage large file handling. This value is in bytes.

```toml
default_max_prompt_size = 204800   # bytes (default: 200KB)
```

--------------------------------

### Manage Agent Skills

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/commands.mdx

Install or update skills for your Roborev agents.

```bash
roborev skills install           # Install skills for agents
roborev skills update            # Update installed skills
```

--------------------------------

### Verify post-commit Hook Installation

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/guides/troubleshooting.mdx

Checks if the roborev post-commit hook is installed correctly by resolving the hooks path and displaying the hook's content. Ensure the hook file contains a 'roborev enqueue' call.

```bash
# Resolves core.hooksPath (relative or absolute) against the main
# repo root, falling back to .git/hooks. Works from linked worktrees.
COMMON="$(git rev-parse --path-format=absolute --git-common-dir)"
HP="$(git config core.hooksPath || true)"
if [ -n "$HP" ]; then
  case "$HP" in /*) HOOKS="$HP" ;; *) HOOKS="${COMMON%.git}/$HP" ;; esac
else
  HOOKS="$COMMON/hooks"
fi
cat "$HOOKS/post-commit"
```

```bash
#!/bin/sh
# roborev post-commit hook - auto-reviews every commit
roborev enqueue --quiet 2>/dev/null
```

--------------------------------

### Get Configuration Values

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/configuration.mdx

Retrieve configuration values using the `roborev config get` command. Specify `--global` for global config, `--local` for repo config, or omit for merged scope (repo then global). Nested keys use dot notation.

```bash
roborev config get default_agent              # merged: tries local, then global
roborev config get default_agent --global     # global config only
roborev config get review_agent --local       # repo config only
roborev config get sync.enabled               # nested keys use dot notation
```

--------------------------------

### Interact with TUI Socket using Bash

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/integrations/tui.mdx

Discover the TUI socket path from runtime metadata and send commands using netcat. This example demonstrates querying the current state and setting a repository filter.

```bash
# Find the socket path from runtime metadata
SOCKET=$(python3 -c "import json,glob; f=glob.glob('$HOME/.roborev/tui.*.json')[0]; print(json.load(open(f))['socket_path'])")

# Query current state
echo '{"command":"get-state"}' | nc -U "$SOCKET"

# Set filter to a specific repo
echo '{"command":"set-filter","params":{"repo":"myproject"}}' | nc -U "$SOCKET"
```

--------------------------------

### Manage Roborev Configuration

Source: https://context7.com/roborev-dev/roborev-docs/llms.txt

Get, set, and list configuration values for Roborev, with options to specify global or repository-specific scopes.

```bash
# Get a value (merged: repo overrides global)
roborev config get agent
```

```bash
# Get from global config only
roborev config get default_agent --global
```

```bash
# Set agent in the current repo's .roborev.toml
roborev config set agent codex
```

```bash
# Set a global default
roborev config set default_agent claude-code --global
```

```bash
# Enable background tasks globally
roborev config set advanced.tasks_enabled true --global
```

```bash
# List full merged config with origin column
roborev config list --show-origin
```

--------------------------------

### Roborev Token Backfill Command Examples

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/commands.mdx

Use `backfill-tokens` to fetch and store token usage data for older jobs. A `--dry-run` option is available for previewing without making changes.

```bash
roborev backfill-tokens             # Fetch token data for all eligible jobs
```

```bash
roborev backfill-tokens --dry-run   # Preview without writing
```

--------------------------------

### Per-Repo Overrides - Backend Repo Configuration

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/integrations/github.mdx

Example of a `.roborev.toml` file in a repository's root directory to override global CI settings. This configuration specifies deeper reviews with multiple agents and thorough reasoning for the backend repository.

```toml
# myorg/backend/.roborev.toml

[ci]
review_types = ["security", "default"]
agents = ["codex", "gemini"]
reasoning = "thorough"
```

--------------------------------

### ACP Configuration Reference

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/advanced/acp.mdx

Example of the ACP configuration section in `~/.roborev/config.toml`, showing various options like name, command, arguments, model, timeout, and mode settings.

```toml
[acp]
name = "my-agent"                  # Agent name (required)
command = "/usr/local/bin/my-acp"  # ACP agent command (required)
args = ["--verbose"]               # Additional arguments
model = "my-model"                 # Default model
timeout = 600                      # Timeout in seconds (default: 600)
read_only_mode = "plan"            # Mode for review flows
auto_approve_mode = "auto-approve" # Mode for agentic flows
disable_mode_negotiation = false   # Skip SetSessionMode RPC
```

--------------------------------

### GitHub App Configuration - Single Review

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/integrations/github.mdx

Configure the GitHub App for a single review type with specified agents and models. Ensure the private key path and installation ID are correct.

```toml
[ci]
enabled = true
poll_interval = "5m"
repos = ["myorg/backend", "myorg/frontend"]
review_types = ["security"]
agents = ["claude-code"]
model = "claude-sonnet-4-5-20250929"

github_app_id = 123456
github_app_private_key = "~/.roborev/roborev.pem"
github_app_installation_id = 12345678
```

--------------------------------

### Per-Repo Overrides - Frontend Repo Configuration

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/integrations/github.mdx

Example of a `.roborev.toml` file for a repository requiring a faster, security-focused review. This configuration overrides global settings to use a single agent for security scans with fast reasoning.

```toml
# myorg/frontend/.roborev.toml

[ci]
review_types = ["security"]
agents = ["codex"]
reasoning = "fast"
```

--------------------------------

### JSON Output for Programmatic Workflows

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/guides/assisted-refactoring.mdx

Example of using the `--json` flag with `roborev analyze` for programmatic output, suitable for agent-driven workflows. This shows the basic JSON structure.

```bash
roborev analyze refactor --json 'cmd/*.go'
```

--------------------------------

### Interact with Daemon REST API

Source: https://context7.com/roborev-dev/roborev-docs/llms.txt

Examples of using `curl` to interact with the Roborev daemon's REST API, which is available on `http://127.0.0.1:7373`. This includes fetching the OpenAPI spec, listing jobs, getting status, and managing reviews.

```bash
# Fetch the OpenAPI spec
curl http://127.0.0.1:7373/openapi.json | jq .
```

```bash
# List review jobs (cursor-based pagination)
curl "http://127.0.0.1:7373/api/jobs?repo=myrepo&branch=main&open=true"
```

```bash
# Get a specific review by job ID
curl "http://127.0.0.1:7373/api/review?job_id=42"
```

```bash
# Get daemon status
curl http://127.0.0.1:7373/api/status | jq '{workers, queue_depth, version}'
```

```bash
# Get aggregate summary
curl "http://127.0.0.1:7373/api/summary?since=7d&repo=myrepo" | jq .
```

```bash
# List repos with job counts
curl http://127.0.0.1:7373/api/repos | jq '.repos[] | {name, open_jobs}'
```

```bash
# Close a review
curl -X POST http://127.0.0.1:7373/api/review/close \
  -H "Content-Type: application/json" \
  -d '{"job_id": 42, "closed": true}'
```

```bash
# Rerun a job
curl -X POST http://127.0.0.1:7373/api/job/rerun \
  -H "Content-Type: application/json" \
  -d '{"job_id": 42}'
```

--------------------------------

### Agent Review-Fix Loop Example

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/guides/reviewing-code.mdx

This demonstrates a typical workflow for a coding agent using `roborev wait` in a review-fix refinement loop. After a commit triggers a review, the agent calls `wait --quiet` to block until the verdict is ready, using the exit code to determine the next steps.

```bash
# Typical agent loop
git commit -m "Fix auth validation"   # Hook triggers review
roborev wait --quiet                  # Block until verdict
# Exit code 0 = pass, 1 = fail
```

--------------------------------

### Run All Tests

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/development.mdx

Execute all tests within the project using the `go test ./...` command. This is useful for ensuring the entire codebase is functioning correctly.

```bash
go test ./...
```

--------------------------------

### Build All Packages

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/development.mdx

Compile all Go packages in the project using `go build ./...`. This command builds all executables and libraries within the project.

```bash
go build ./...
```

--------------------------------

### Initialize Roborev

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/commands.mdx

Initializes the repository, daemon, and hook. Use `--no-daemon` to skip auto-starting the daemon.

```bash
roborev init [--agent <name>]    # Initialize repo + daemon + hook
                                 # --no-daemon: skip auto-starting daemon
```

--------------------------------

### Viewing and Listing Reviews

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/commands.mdx

Use these commands to view specific reviews by commit SHA or job ID, list available jobs, or open an interactive terminal UI.

```bash
roborev show                     # Show review for HEAD
roborev show <sha>               # Show review for commit
roborev show <job_id>            # Show review by job ID
roborev show --job <id>          # Force interpretation as job ID
roborev show --prompt <job_id>   # Show the prompt sent to the agent
roborev list                     # List jobs for current repo/branch
roborev list --open              # List only open reviews
roborev list --closed            # List only closed reviews
roborev tui                      # Interactive browser
roborev tui --repo --branch      # Pre-filtered to current repo+branch
```

--------------------------------

### Linux Systemd Socket Activation for Roborev

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/configuration.mdx

Enable and start the Roborev socket unit on Linux for on-demand daemon startup via socket activation. The daemon starts automatically when a client connects.

```bash
systemctl --user enable --now roborev.socket
```

--------------------------------

### Review Commits Since a Specific Point

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/guides/reviewing-code.mdx

Use the `--since` flag to specify a starting point for the review. The range is exclusive of the starting commit, similar to Git's `..` syntax.

```bash
roborev review --since HEAD~5       # Review last 5 commits
roborev review --since abc123       # Review commits since abc123 (exclusive)
roborev review --since v1.0.0       # Review commits since a tag
```

--------------------------------

### Filtering with jq

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/advanced/streaming.mdx

Examples of using `jq` to filter the streamed events.

```bash
# Only completed reviews
roborev stream | jq -c 'select(.type == "review.completed")'

# Only failures
roborev stream | jq -c 'select(.type == "review.failed")'

# Specific repo
roborev stream | jq -c 'select(.repo_name == "myproject")'

# Failed verdicts
roborev stream | jq -c 'select(.verdict == "F")'
```

--------------------------------

### Show Review Details

Source: https://context7.com/roborev-dev/roborev-docs/llms.txt

Use 'roborev show' to display review details by commit SHA or job ID. Options include showing the agent prompt or outputting in JSON format for scripting.

```bash
roborev show a1b2c3d
```

```bash
roborev show 42
```

```bash
roborev show --prompt 42
```

```bash
roborev show --json 42
```

--------------------------------

### Configure Prompt Size Budget

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/configuration.mdx

Set the maximum prompt size in bytes for review agents using `max_prompt_size` (per repo) and `default_max_prompt_size` (global). The per-repo value takes precedence. The default is 200,000 bytes.

```toml
# ~/.roborev/config.toml
default_max_prompt_size = 300000   # 300 KB global default
```

```toml
# .roborev.toml
max_prompt_size = 500000           # 500 KB for this repo only
```

--------------------------------

### roborev skills

Source: https://context7.com/roborev-dev/roborev-docs/llms.txt

Install bundled skills so coding agents can invoke roborev directly from within their session.

```APIDOC
## Agent Skills — Slash commands inside coding agents

Install bundled skills so coding agents can invoke roborev directly from within their session.

### Usage

```bash
# Install skills for all detected agents
roborev skills install

# Update installed skills
roborev skills update

# Check installation status per agent
roborev skills
# Output:
#   claude-code  roborev-review          installed  (v0.54)
#   claude-code  roborev-fix             installed  (v0.54)
#   codex        roborev-review          installed  (v0.54)
#   codex        roborev-fix             outdated   (v0.50 → v0.54)
```

### Agent Commands

```
# Inside Claude Code session — trigger a review
/roborev-review

# Review the current branch
/roborev-review-branch

# Security review
/roborev-design-review

# Fix all open reviews on this branch
/roborev-fix

# Run iterative refine loop
/roborev-refine

# Add a response/comment to a review
/roborev-respond

# Inside Codex session ($ prefix instead of /)
$roborev-fix
$roborev-review-branch
```
```

--------------------------------

### Check Roborev Agents

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/integrations/github.mdx

Smoke-test all installed AI agents or a specific agent to ensure they are functioning correctly.

```bash
roborev check-agents             # smoke-test all installed agents
roborev check-agents --agent codex  # test a specific agent
```

--------------------------------

### Manage Roborev Daemon and Queue

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/commands.mdx

Commands for fixing issues, checking status, and getting summaries or insights.

```bash
roborev fix                      # Fix open reviews
roborev status                   # Check daemon and queue
roborev summary                  # Aggregate review statistics
roborev insights                 # Analyze review patterns
```

--------------------------------

### roborev check-agents

Source: https://context7.com/roborev-dev/roborev-docs/llms.txt

Smoke-test agent availability. Verifies each installed agent is reachable, configured, and capable of producing a review.

```APIDOC
## `roborev check-agents` — Smoke-test agent availability

Verifies each installed agent is reachable, configured, and capable of producing a review.

### Usage

```bash
# Test all detected agents
roborev check-agents

# Test a specific agent
roborev check-agents --agent claude-code

# Set per-agent timeout
roborev check-agents --timeout 30

# Example output:
# codex        ✓ available  (gpt-5.2-codex)
# claude-code  ✓ available  (claude-opus-4-5)
# gemini       ✗ unavailable: GOOGLE_API_KEY not set
```
```

--------------------------------

### Set Review Guidelines for a Repository

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/configuration.mdx

Use the `review_guidelines` option to provide project-specific context to the AI reviewer. This helps suppress irrelevant warnings, enforce conventions, or describe trust boundaries and architecture.

```toml
review_guidelines = """
This is a local CLI tool. The daemon runs on localhost and all
displayed data originates from the user's own filesystem and git
repos. Do not flag injection or sanitization for data that never
crosses a trust boundary.

Performance is critical - flag any O(n^2) or worse algorithms.
All error messages must be user-friendly.
"""
```

--------------------------------

### Control Roborev Daemon

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/commands.mdx

Start, stop, restart, or run the Roborev background daemon. The `run` command executes it in the foreground.

```bash
roborev daemon start             # Start background daemon
roborev daemon stop              # Stop daemon
roborev daemon restart           # Restart daemon
roborev daemon run               # Run in foreground
```

--------------------------------

### Configure PostgreSQL Sync

Source: https://context7.com/roborev-dev/roborev-docs/llms.txt

Enable and configure bidirectional synchronization of the local SQLite review database to a PostgreSQL instance. Requires setting the 'postgres_url' and 'machine_name'.

```toml
# ~/.roborev/config.toml
[sync]
enabled = true
postgres_url = "postgres://roborev:${ROBOREV_PG_PASS}@db.tailnet:5432/roborev"
interval = "1h"
machine_name = "workstation"
```

--------------------------------

### Configure Multi-Review Types and Agents

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/integrations/github.mdx

Enable CI, set a poll interval, and specify repositories. Configure multiple `review_types` and `agents` to run in parallel, creating a matrix of jobs for each PR. Synthesis is skipped for a 1x1 matrix.

```toml
[ci]
enabled = true
poll_interval = "5m"
repos = ["myorg/myrepo"]

# Run both security and standard code reviews
review_types = ["security", "default"]

# Use multiple agents
agents = ["codex", "gemini"]

# This creates 4 jobs per PR (2 types x 2 agents)

```

--------------------------------

### Preview Refinements Without Running Agents

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/guides/auto-fixing.mdx

Use `--list` to preview which reviews would be refined without executing any agents. This can be applied to the current branch or all branches, with an option to sort by newest first.

```bash
roborev refine --list                    # Current branch
```

```bash
roborev refine --list --all-branches     # All branches
```

```bash
roborev refine --list --newest-first     # Newest first
```

--------------------------------

### Check Roborev Agents

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/commands.mdx

Perform a smoke test on all installed agents or a specific agent. Set a custom timeout for each agent test.

```bash
roborev check-agents                # Smoke-test all installed agents
roborev check-agents --agent codex  # Test a specific agent
roborev check-agents --timeout 30   # Set timeout per agent (seconds)
```

--------------------------------

### GitHub Issue Creation for Review Failure

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/guides/hooks.mdx

Create a GitHub issue when a review fails. Requires the 'gh' CLI to be installed and authenticated.

```toml
[[hooks]]
event = "review.failed"
command = "gh issue create --title 'roborev: review failed for {sha}' --body 'Review job {job_id} failed. Run `roborev show {job_id}` for details.' --label bug"
```

--------------------------------

### Initialize GitHub Actions Workflow

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/integrations/github.mdx

Use the roborev CLI to quickly generate a GitHub Actions workflow file for CI reviews. This command sets up the basic structure for integrating roborev into your CI pipeline.

```bash
cd your-repo
roborev init gh-action --agent claude-code
```

--------------------------------

### Initialize roborev in a Git Repository

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/index.mdx

Installs the roborev post-commit hook within a Git repository to enable automatic code reviews.

```bash
roborev init
```

--------------------------------

### TUI Protocol Examples

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/integrations/tui.mdx

Send JSON requests to the TUI control socket. Responses indicate success or failure with optional data.

```json
{"command": "get-state"}
```

```json
{"command": "set-filter", "params": {"repo": "myrepo", "branch": "main"}}
```

```json
{"command": "close-review", "params": {"job_id": 42}}
```

```json
{"ok": true, "data": {"view": "queue", "job_count": 15, ...}}
```

```json
{"ok": false, "error": "job not found"}
```

--------------------------------

### Initialize GitHub Actions Workflow

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/commands.mdx

Generate a GitHub Actions workflow file for Roborev. Specify agents, output path, and optionally force overwrite or pin a specific Roborev version.

```bash
roborev init gh-action                          # Generate workflow file
```

```bash
roborev init gh-action --agent codex            # Specify agents
```

```bash
roborev init gh-action --output .github/workflows/review.yml
```

```bash
roborev init gh-action --force                  # Overwrite existing
```

```bash
roborev init gh-action --roborev-version 0.34.0 # Pin version
```

--------------------------------

### Configure PostgreSQL Sync

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/advanced/postgres-sync.mdx

Enable and configure PostgreSQL sync in the roborev configuration file. Ensure sensitive values like passwords are handled securely, potentially using environment variables.

```toml
# ~/.roborev/config.toml
[sync]
enabled = true
postgres_url = "postgres://roborev:${ROBOREV_PG_PASS}@nas.tailnet:5432/roborev"
interval = "1h"           # Sync interval (default: 1h)
machine_name = "laptop"   # Friendly name for this machine
```

```toml
postgres_url = "postgres://roborev:${ROBOREV_PG_PASS}@host:5432/db"
```

--------------------------------

### Initialize Roborev Daemon

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/integrations/github.mdx

Initialize the Roborev daemon, either automatically or with manual daemon management. This command also matches GitHub repos to local checkouts.

```bash
cd /path/to/myrepo
roborev init              # starts daemon automatically
roborev init --no-daemon  # if using systemd/launchd to manage the daemon
```

--------------------------------

### Update Roborev Skills

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/guides/agent-skills.mdx

Execute `roborev update` to automatically update all installed agent skills. This command ensures your skills are running the latest versions.

```bash
roborev update
```

--------------------------------

### Check roborev Daemon Status

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/guides/troubleshooting.mdx

Verifies if the roborev daemon is running. If stopped, it can be started using the provided command. This is essential for processing enqueued commits.

```bash
roborev status
```

```bash
roborev daemon start
```

--------------------------------

### Global CI Configuration

Source: https://github.com/roborev-dev/roborev-docs/blob/main/src/content/docs/integrations/github.mdx

Default CI configuration settings in `~/.roborev/config.toml`. This serves as the baseline for all repositories unless overridden by a per-repo `.roborev.toml` file.

```toml
[ci]
enabled = true
poll_interval = "5m"
repos = ["myorg/backend", "myorg/frontend"]
review_types = ["security"]
agents = ["codex"]

github_app_id = 123456
github_app_private_key = "~/.roborev/roborev.pem"
github_app_installation_id = 12345678
```