How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

reviewer - Prompt - OpenSmartRoute

Name: reviewer
Author: stardustsuperwizard

Prompt file imported from stardustsuperwizard/mikeys_game_bones-rules-moba (.claude/commands/reviewer.md). Fill in {{arguments}} before use. Copyright stays with the author.

Review pull request #{{arguments}} in stardustsuperwizard/mikeys_game_bones-rules-moba.

GitHub access

gh exists in a desktop terminal and does not exist in a cloud session (Claude Code on the web, the Claude mobile app). Settle which one you are in once, with one command, before any GitHub call:

command -v gh >/dev/null 2>&1 && echo ENV=LOCAL || echo ENV=CLOUD

ENV=LOCAL — use the LOCAL form at each call site below.
ENV=CLOUD — use the CLOUD form. gh is absent by design: do not install it, do not curl the REST API, do not go looking for a token, and do not treat its absence as an error worth reporting.

Every call site below gives you both forms, written out in full. Use them verbatim. Never translate one form into the other yourself, and never guess a tool name. The CLOUD tools may need their schema loaded first — if one is not already callable, run ToolSearch once with select:<tool-name>, then call it.

Repository is always owner="stardustsuperwizard", repo="mikeys_game_bones-rules-moba".

First fetch it and the Issue it closes so you have real content to hand off, not a guess:

# LOCAL
gh pr view {{arguments}} --repo stardustsuperwizard/mikeys_game_bones-rules-moba \
  --json number,title,body,url,headRefName,isDraft,files
gh pr diff {{arguments}} --repo stardustsuperwizard/mikeys_game_bones-rules-moba

CLOUD — two calls to mcp__github__pull_request_read, same arguments except
`method`:
  method="get"       -> number, title, body, url, head.ref, draft
  method="get_diff"  -> the diff
  owner="stardustsuperwizard"
  repo="mikeys_game_bones-rules-moba"
  pullNumber={{arguments}}

If the PR doesn't exist or is still a draft, say so and confirm with the user before proceeding anyway — reviewing a draft against acceptance criteria that aren't finished yet produces a misleading verdict.

Otherwise, delegate the review to the reviewer subagent, giving it the PR number and the fetched content above as context.

If the invoker passed a CI outcome — /execute-task does, having just watched the checks settle — pass it through verbatim: green, red with the failing job's output, "no checks applied", or "CI suppressed". A reviewer that is not told CI is red reviews around it and hands back a PASS on a PR that cannot merge. If nobody passed one, say in the report that the verdict was reached without a CI result rather than implying the checks were green.

Install reviewer and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

Review pull request #{{arguments}} in stardustsuperwizard/mikeys_game_bones-rules-moba. ## GitHub access `gh` exists in a desktop terminal and does **not** exist in a cloud session (Claude Code on the web, the Claude mobile app). Settle which one you are in once, with one command, before any GitHub call: ```bash command -v gh >/dev/null 2>&1 && echo ENV=LOCAL || echo ENV=CLOUD ``` - `ENV=LOCAL` — use the `LOCAL` form at each call site below. - `ENV=CLOUD` — use the `CLOUD` form. `gh` is absent by design: do not install it, do not curl the REST API, do not go looking for a token, and do not treat its absence as an error worth reporting. Every call site below gives you both forms, written out in full. Use them verbatim. Never translate one form into the other yourself, and never guess a tool name. The `CLOUD` tools may need their schema loaded first — if one is not already callable, run `ToolSearch` once with `select:<tool-name>`, then call it. Repository is always `owner="stardustsuperwizard"`, `repo="mikeys_game_bones-rules-moba"`. First fetch it and the Issue it closes so you have real content to hand off, not a guess: ```bash # LOCAL gh pr view {{arguments}} --repo stardustsuperwizard/mikeys_game_bones-rules-moba \ --json number,title,body,url,headRefName,isDraft,files gh pr diff {{arguments}} --repo stardustsuperwizard/mikeys_game_bones-rules-moba ``` ```text CLOUD — two calls to mcp__github__pull_request_read, same arguments except `method`: method="get" -> number, title, body, url, head.ref, draft method="get_diff" -> the diff owner="stardustsuperwizard" repo="mikeys_game_bones-rules-moba" pullNumber={{arguments}} ``` If the PR doesn't exist or is still a draft, say so and confirm with the user before proceeding anyway — reviewing a draft against acceptance criteria that aren't finished yet produces a misleading verdict. Otherwise, delegate the review to the `reviewer` subagent, giving it the PR number and the fetched content above as context. If the invoker passed a CI outcome — `/execute-task` does, having just watched the checks settle — pass it through verbatim: green, red with the failing job's output, "no checks applied", or "CI suppressed". A reviewer that is not told CI is red reviews around it and hands back a `PASS` on a PR that cannot merge. If nobody passed one, say in the report that the verdict was reached without a CI result rather than implying the checks were green.

{ "prompt": "Review pull request #{{arguments}} in stardustsuperwizard/mikeys_game_bones-rules-moba.\n\n## GitHub access\n\n`gh` exists in a desktop terminal and does **not** exist in a cloud session\n(Claude Code on the web, the Claude mobile app). Settle which one you are in\nonce, with one command, before any GitHub call:\n\n```bash\ncommand -v gh >/dev/null 2>&1 && echo ENV=LOCAL || echo ENV=CLOUD\n```\n\n- `ENV=LOCAL` — use the `LOCAL` form at each call site below.\n- `ENV=CLOUD` — use the `CLOUD` form. `gh` is absent by design: do not\n install it, do not curl the REST API, do not go looking for a token, and\n do not treat its absence as an error worth reporting.\n\nEvery call site below gives you both forms, written out in full. Use them\nverbatim. Never translate one form into the other yourself, and never guess\na tool name. The `CLOUD` tools may need their schema loaded first — if one\nis not already callable, run `ToolSearch` once with `select:<tool-name>`,\nthen call it.\n\nRepository is always `owner=\"stardustsuperwizard\"`,\n`repo=\"mikeys_game_bones-rules-moba\"`.\n\nFirst fetch it and the Issue it closes so you have real content to hand\noff, not a guess:\n\n```bash\n# LOCAL\ngh pr view {{arguments}} --repo stardustsuperwizard/mikeys_game_bones-rules-moba \\\n --json number,title,body,url,headRefName,isDraft,files\ngh pr diff {{arguments}} --repo stardustsuperwizard/mikeys_game_bones-rules-moba\n```\n\n```text\nCLOUD — two calls to mcp__github__pull_request_read, same arguments except\n`method`:\n method=\"get\" -> number, title, body, url, head.ref, draft\n method=\"get_diff\" -> the diff\n owner=\"stardustsuperwizard\"\n repo=\"mikeys_game_bones-rules-moba\"\n pullNumber={{arguments}}\n```\n\nIf the PR doesn't exist or is still a draft, say so and confirm with the\nuser before proceeding anyway — reviewing a draft against acceptance\ncriteria that aren't finished yet produces a misleading verdict.\n\nOtherwise, delegate the review to the `reviewer` subagent, giving it the PR\nnumber and the fetched content above as context.\n\nIf the invoker passed a CI outcome — `/execute-task` does, having just\nwatched the checks settle — pass it through verbatim: green, red with the\nfailing job's output, \"no checks applied\", or \"CI suppressed\". A reviewer\nthat is not told CI is red reviews around it and hands back a `PASS` on a PR\nthat cannot merge. If nobody passed one, say in the report that the verdict\nwas reached without a CI result rather than implying the checks were green.", "variables": [ "arguments" ], "notes": "Review a pull request against its Implementation Task Issue's acceptance criteria and publish a verdict (local counterpart of the agent:reviewer:copilot label) Arguments: <pr-number>.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/stardustsuperwizard/mikeys_game_bones-rules-moba", "path": ".claude/commands/reviewer.md", "ref": "ef29ad3bc7f49834df764f0593702f3621d227c4", "url": "https://github.com/stardustsuperwizard/mikeys_game_bones-rules-moba/blob/ef29ad3bc7f49834df764f0593702f3621d227c4/.claude/commands/reviewer.md", "key": "stardustsuperwizard/mikeys_game_bones-rules-moba/.claude/commands/reviewer.md" } } }

reviewer

About

GitHub access

Install reviewer and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews