Dispatch Infrastructure

This skill provides shared infrastructure for multi-model CLI dispatch. It is NOT user-invocable — it exists as reference material for the adv-review orchestrator agent and the adv-* commands.

Available Engines

Scripts

preflight.sh

Path: ${CLAUDE_PLUGIN_ROOT}/skills/dispatch/scripts/preflight.sh

Combined pre-flight check: dependency verification, engine health checks, and scope resolution in a single call.

# Smart default (uncommitted changes > last commit > full repo)
bash preflight.sh

# Explicit scope modes
bash preflight.sh --commits abc123..def456
bash preflight.sh --since HEAD~5
bash preflight.sh --full

Arguments:

• --commits <range> — Review a specific commit range.
• --since <ref> — Review changes since a commit/ref.
• --full — Full repo file manifest.
• (no flags) — Smart default: uncommitted changes > last commit > full repo.

Output: Single JSON object to stdout:

{
  "deps": {"codex": true, "gemini": true, "claude": true, "jq": true},
  "engines": {
    "codex": {"available": true, "error_type": "none"},
    "gemini": {"available": true, "error_type": "none", "model": "gemini-2.5-pro"}
  },
  "scope": {
    "type": "working",
    "files_changed": 5,
    "diff_lines": 120,
    "untracked_files": 2,
    "content_file": ".claude/reviews/.tmp/scope-content.txt"
  }
}

Scope types: working (uncommitted changes), commits (commit range/since), full (file manifest).

Internally calls dispatch.sh --health-check for engine verification, including automatic Gemini flash fallback on quota errors.

run-phase.sh

Path: ${CLAUDE_PLUGIN_ROOT}/skills/dispatch/scripts/run-phase.sh

Parallel dispatch orchestrator for review and cross-examination phases. Handles dispatch, validation, and fallback in a single call.

# Review phase — dispatch 4 reviewers in parallel
bash run-phase.sh --phase review \
  --assignments "quality:codex,implementation:gemini,testing:codex,documentation:gemini" \
  --prompt-dir "$TMP" --output-dir "$TMP" --timeout 300

# Cross-exam phase — dispatch 2 engines in parallel
bash run-phase.sh --phase cross-exam --round 1 \
  --assignments "codex,gemini" \
  --prompt-dir "$TMP" --output-dir "$TMP" --timeout 300

Arguments:

• --phase <review|cross-exam> — Required. Phase type.
• --assignments <spec> — Required. Engine assignments.
  • Review: "quality:codex,implementation:gemini,testing:codex,documentation:gemini"
  • Cross-exam: "codex,gemini" (just engine names)
• --prompt-dir <path> — Directory containing prepared prompt files.
• --output-dir <path> — Directory for output files.
• --timeout <seconds> — Timeout per dispatch (default: 300).
• --round <N> — Cross-exam round number (required for cross-exam phase).
• --gemini-model <model> — Override Gemini model (e.g., gemini-2.0-flash).

File naming conventions:

• Review prompts: prompt-<reviewer>.md (e.g., prompt-quality.md)
• Review findings: findings-<reviewer>.md (e.g., findings-quality.md)
• Cross-exam prompts: prompt-xr<N>.md (e.g., prompt-xr1.md)
• Cross-exam results: xr<N>-<engine>.md (e.g., xr1-codex.md, xr1-gemini.md)

Output: JSON summary to stdout:

{
  "phase": "review",
  "results": {
    "quality": {"engine": "codex", "status": "success", "fallback_used": false}
  },
  "success_count": 4,
  "failed": []
}

Cross-exam output also includes verdict counts:

{
  "phase": "cross-exam",
  "round": 1,
  "verdicts": {"validate": 8, "dispute": 2, "amend": 1, "new_findings": 0}
}

Fallback logic (review phase only):

1. If Gemini dispatch fails with quota, retries with gemini-2.0-flash
2. If still failed, falls back to Claude
3. Final status reported in JSON output

dispatch.sh

Path: ${CLAUDE_PLUGIN_ROOT}/skills/dispatch/scripts/dispatch.sh

Core single-model CLI dispatcher. Called internally by preflight.sh and run-phase.sh, and directly by the /adv-codex, /adv-gemini, /adv-gemini-research commands.

# Basic dispatch
bash dispatch.sh --engine codex --prompt "Review this code" --cwd /path/to/repo

# With output file and prompt file
bash dispatch.sh --engine gemini --prompt-file /path/to/prompt.md --output-file /tmp/findings.md

# Research mode (Gemini only)
bash dispatch.sh --engine gemini --research --prompt "Latest TypeScript best practices"

# Check prerequisites
bash dispatch.sh --check-deps

# Health check
bash dispatch.sh --engine codex --health-check

Arguments:

• --engine <codex|gemini|claude> — Required. Target engine.
• --prompt <string> — The prompt text. Mutually exclusive with --prompt-file.
• --prompt-file <path> — Read prompt from a file.
• --model <model> — Override the default model for the engine.
• --cwd <path> — Working directory for the CLI (default: current dir).
• --timeout <seconds> — Max execution time (default: 300).
• --output-file <path> — Write response to this file.
• --research — Gemini only: enable grounded search.
• --check-deps — Check for required CLIs and exit with report.
• --health-check — Quick ping to verify engine is responsive (30s timeout, minimal prompt).

Exit Codes (classified by error type):

Output Contract:

• Response text (markdown) is written to --output-file if specified.
• On failure, the output file contains DISPATCH_ERROR: engine=<e> exit_code=<n> duration_ms=<ms> so the orchestrator can detect failures by reading the file.
• A JSON status line is printed to stdout: {"engine":"codex","success":true,"output_file":"/path","duration_ms":12345,"exit_code":0,"error_type":"none","model":"default"}
• Stderr is logged to .claude/reviews/.tmp/dispatch.log

API Key Resolution (Gemini):

1. Checks GOOGLE_API_KEY env var
2. Falls back to GEMINI_API_KEY env var
3. If neither set and op + ~/.env available, wraps Gemini calls with op run --env-file to inject from 1Password

scope.sh

Path: ${CLAUDE_PLUGIN_ROOT}/skills/dispatch/scripts/scope.sh

Standalone git scope resolver. Used by the ad-hoc commands. The orchestrator uses preflight.sh instead (which includes scope resolution).

# Smart default (uncommitted changes > last commit > full repo)
bash scope.sh

# Explicit modes
bash scope.sh --commits abc123..def456
bash scope.sh --since HEAD~5
bash scope.sh --full

Output: JSON to stdout with scope type and artifact paths.

Prompts

Reviewer prompt templates are in ${CLAUDE_PLUGIN_ROOT}/skills/dispatch/prompts/:

Each reviewer prompt contains a {SCOPE_CONTENT} placeholder that the orchestrator replaces with the actual scope content (diff or manifest) before dispatch.