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.

90 days of the enterprise, pro and team plans free, no card needed. See the plans

OpenSmartRoute

review-pr - Prompt - OpenSmartRoute

Promptv1.0.0

review-pr

Name: review-pr
Author: brublurryface

Perform a final quality review of a pull request

by brublurryface(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Prompt file imported from brublurryface/sanaka (.github/prompts/review-pr.prompt.md). Fill in {{prNumber}} before use. Copyright stays with the author.

Review this Sanaka pull request:

Do not modify files. Do not merge the pull request.

Use GitHub CLI to inspect:

title and body
base and head branches
state and mergeability
changed files
additions and deletions
commits
status checks
complete diff

Review the diff for:

unexpected files
accidental debug code
obsolete Angular patterns
unnecessary complexity
incorrect RxJS usage
test problems
accessibility regressions
maintainability problems
unrelated changes

Do not request cosmetic redesign unless visual design is part of the pull request scope.

Finish with exactly one conclusion:

READY TO MERGE

CHANGES RECOMMENDED

If changes are recommended, explain precisely what should change and why.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

Review this Sanaka pull request:

{{prNumber}}

Do not modify files.
Do not merge the pull request.

Use GitHub CLI to inspect:

- title and body
- base and head branches
- state and mergeability
- changed files
- additions and deletions
- commits
- status checks
- complete diff

Review the diff for:

- unexpected files
- accidental debug code
- obsolete Angular patterns
- unnecessary complexity
- incorrect RxJS usage
- test problems
- accessibility regressions
- maintainability problems
- unrelated changes

Do not request cosmetic redesign unless visual design is part of the pull request scope.

Finish with exactly one conclusion:

READY TO MERGE

or

CHANGES RECOMMENDED

If changes are recommended, explain precisely what should change and why.

Installed into a catalogue, chosen by a router

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

Photo: RDNE Stock project

For the business

What it costs to adopt - in engineering time.

Same client, same code
One base URL
The OpenAI-compatible endpoint answers your existing SDK calls; model=auto lets the router choose.
The SDKs
One URL, every vendor
No vendor lock-in
Point your OpenAI-compatible client at one address; add, swap or retire providers in the catalogue without touching application code.
Every vendor side by side
Next eligible model answers
Failover built in
When a provider is down or over quota the request moves on; the trace says it did.

Manifest

The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.

brublurryface-sanaka-review-pr-prompt.prompt.jsonjson

{
  "prompt": "Review this Sanaka pull request:\n\n{{prNumber}}\n\nDo not modify files.\nDo not merge the pull request.\n\nUse GitHub CLI to inspect:\n\n- title and body\n- base and head branches\n- state and mergeability\n- changed files\n- additions and deletions\n- commits\n- status checks\n- complete diff\n\nReview the diff for:\n\n- unexpected files\n- accidental debug code\n- obsolete Angular patterns\n- unnecessary complexity\n- incorrect RxJS usage\n- test problems\n- accessibility regressions\n- maintainability problems\n- unrelated changes\n\nDo not request cosmetic redesign unless visual design is part of the pull request scope.\n\nFinish with exactly one conclusion:\n\nREADY TO MERGE\n\nor\n\nCHANGES RECOMMENDED\n\nIf changes are recommended, explain precisely what should change and why.",
  "variables": [
    "prNumber"
  ],
  "notes": "Perform a final quality review of a pull request Arguments: pull request number.",
  "metadata": {
    "source": {
      "provider": "github-prompts",
      "repository": "https://github.com/brublurryface/sanaka",
      "path": ".github/prompts/review-pr.prompt.md",
      "ref": "f0ed87fdf142c99e019552954279a50a3cd5f37d",
      "url": "https://github.com/brublurryface/sanaka/blob/f0ed87fdf142c99e019552954279a50a3cd5f37d/.github/prompts/review-pr.prompt.md",
      "key": "brublurryface/sanaka/.github/prompts/review-pr.prompt.md"
    }
  }
}

Fetch it by URL: GET /api/v1/registry/brublurryface-sanaka-review-pr-prompt/manifest?version=1.0.0

About

Use it

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