sonichi / claude-router

Claude Router

Route a task from Claude Code to local codex, gemini, or pi using simple, explicit rules. This skill assumes the dedicated claude-codex, claude-gemini, and claude-pi skills are installed from this repo.

Usage: /claude-router [prompt]

ARGUMENTS: $ARGUMENTS

Routing Rules

• Route to codex for:

  • code review
  • bug hunting in a small or medium code slice
  • implementation requests
  • patch validation on current changes

• Route to gemini for:

  • repo-wide scans
  • architecture and dependency tracing
  • large-context summarization
  • multimodal or structured JSON output requests

• Route to pi when:

  • the request names pi or kimi
  • the user wants a Kimi-family second opinion

If the request explicitly names codex, gemini, or pi, honor that directly.

When NOT to Use

• Interactive code review or task hand-off from this Claude Code session → use the /codex:* plugin commands directly (/codex:review, /codex:adversarial-review, /codex:rescue, /codex:status). The router is for programmatic delegation from scripts, cron, and bridges — it goes through the claude-codex skill's bash wrapper, not the plugin.

  If you don't see /codex:* slash-commands, install the plugin via the 4 commands documented in skills/claude-codex/SKILL.md ("When NOT to Use" section).

Default Behavior

• Default review-oriented prompts to Codex.
• Default broad analysis prompts to Gemini in plan approval mode.
• Keep execution in the current workspace unless the user requested a different directory.

Quick Checks

bash "$SKILL_DIR/scripts/route-ai.sh" --check

Common Commands

# Auto-route based on prompt
bash "$SKILL_DIR/scripts/route-ai.sh" -- "Review the current diff for regressions"

# Force Codex
bash "$SKILL_DIR/scripts/route-ai.sh" --engine codex -- "Inspect src/task-bridge.ts for races"

# Force Gemini
bash "$SKILL_DIR/scripts/route-ai.sh" --engine gemini -- "Trace task flow across the entire repo"

# Force Pi (Kimi)
bash "$SKILL_DIR/scripts/route-ai.sh" --engine pi -- "Second opinion on this design"

# Dry-run the route decision without executing
bash "$SKILL_DIR/scripts/route-ai.sh" --dry-run -- "Summarize architecture risks in this repo"

If Invoked As A Slash Command

• If ARGUMENTS is empty, explain the route rules and suggest a plain prompt.
• If ARGUMENTS is present, run:

bash "$SKILL_DIR/scripts/route-ai.sh" -- "$ARGUMENTS"