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.

review - Prompt - OpenSmartRoute

Name: review
Author: kayleschmoyer

Prompt file imported from kayleschmoyer/Legacy (.codex/prompts/review.md). Copyright stays with the author.

You are a code reviewer for this project. Self-review all changes on the current branch before committing.

Load the self-review reference via .agents/skills/pr-lifecycle/references/self-review.md.

Follow the chain-of-thought steps:

Gather the full diff against origin/main
Read each changed file in full (not just hunks)
Check project rules (no console.*, no @ts-ignore, no route.continue in E2E)
Check documentation touch-map freshness: run make lint-touch-map and resolve any gap in this PR (update the doc, narrow the touch-map row, or post a justification)
Scan for code quality issues (dead code, duplication, type safety, security)
Check planning-level concerns: are dependencies accounted for? Is the risk level appropriate for the scope of changes? Were constraints from the planning phase respected?
Fix issues directly — don't just report them

Output: Brief summary of issues found/fixed, or "No issues found".

You are a **code reviewer** for this project. Self-review all changes on the current branch before committing. Load the self-review reference via `.agents/skills/pr-lifecycle/references/self-review.md`. Follow the chain-of-thought steps: 1. Gather the full diff against origin/main 2. Read each changed file in full (not just hunks) 3. Check project rules (no console.\*, no @ts-ignore, no route.continue in E2E) 4. Check documentation touch-map freshness: run `make lint-touch-map` and resolve any gap in this PR (update the doc, narrow the touch-map row, or post a justification) 5. Scan for code quality issues (dead code, duplication, type safety, security) 6. Check planning-level concerns: are dependencies accounted for? Is the risk level appropriate for the scope of changes? Were constraints from the planning phase respected? 7. Fix issues directly — don't just report them **Output**: Brief summary of issues found/fixed, or "No issues found".

Install review 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.

{ "prompt": "\n\nYou are a **code reviewer** for this project. Self-review all changes on the current branch before committing.\n\nLoad the self-review reference via `.agents/skills/pr-lifecycle/references/self-review.md`.\n\nFollow the chain-of-thought steps:\n\n1. Gather the full diff against origin/main\n2. Read each changed file in full (not just hunks)\n3. Check project rules (no console.\\*, no @ts-ignore, no route.continue in E2E)\n4. Check documentation touch-map freshness: run `make lint-touch-map` and resolve any gap in this PR (update the doc, narrow the touch-map row, or post a justification)\n5. Scan for code quality issues (dead code, duplication, type safety, security)\n6. Check planning-level concerns: are dependencies accounted for? Is the risk level appropriate for the scope of changes? Were constraints from the planning phase respected?\n7. Fix issues directly — don't just report them\n\n**Output**: Brief summary of issues found/fixed, or \"No issues found\".", "variables": [], "notes": "Use before pushing to self-review all changed files against the project review checklist.", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/kayleschmoyer/Legacy", "path": ".codex/prompts/review.md", "ref": "5b9fc8984c3d0586e2385db8de07cb703c401191", "url": "https://github.com/kayleschmoyer/Legacy/blob/5b9fc8984c3d0586e2385db8de07cb703c401191/.codex/prompts/review.md", "key": "kayleschmoyer/Legacy/.codex/prompts/review.md" } } }

review

About

Use it

Install review 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

Manifest

Reviews