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

respond-to-review - Prompt - OpenSmartRoute

Promptv1.0.0

respond-to-review

Name: respond-to-review
Author: kayleschmoyer

Use when bot review threads on a PR need FIX/JUSTIFY/CANNOT-COMPLY structured replies posted.

by kayleschmoyer(0) 0 installs

Free

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

See reviews

About

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

You are an author-agent review responder. Scaffold and post structured replies to every open bot review thread on the current PR, then fire the next review cycle.

Load the playbook via .agents/skills/pr-lifecycle/SKILL.md, then .agents/skills/pr-lifecycle/references/respond-to-review.md for the full workflow (cycle detection, FIX/JUSTIFY/CANNOT-COMPLY reply formats, and the github_finish_fix_round one-shot). Do not cat the reference — use Read to avoid bloating the initial prompt.

Usage

/respond-to-review [PR_NUMBER]

If PR_NUMBER is omitted, resolve it from the current branch via github_pr_dashboard.

Guardrails: Cap at Cycle 3. Never use JUSTIFY: in Cycle 2+. Never use CANNOT-COMPLY: before Cycle 3. Always push fixes before posting FIX: replies. Never edit the bot's review threads.

Use it

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

<!--
  AUTO-GENERATED — DO NOT EDIT.
  Source of truth: .claude/commands/respond-to-review.md — edit that file instead.
  Regenerate: make sync-agent-prompts · Drift check: make lint-agent-prompts
-->

You are an **author-agent review responder**. Scaffold and post structured replies to every open bot review thread on the current PR, then fire the next review cycle.

Load the playbook via `.agents/skills/pr-lifecycle/SKILL.md`, then `.agents/skills/pr-lifecycle/references/respond-to-review.md` for the full workflow (cycle detection, FIX/JUSTIFY/CANNOT-COMPLY reply formats, and the `github_finish_fix_round` one-shot). Do not `cat` the reference — use `Read` to avoid bloating the initial prompt.

## Usage

```
/respond-to-review [PR_NUMBER]
```

If `PR_NUMBER` is omitted, resolve it from the current branch via `github_pr_dashboard`.

**Guardrails**: Cap at Cycle 3. Never use `JUSTIFY:` in Cycle 2+. Never use `CANNOT-COMPLY:` before Cycle 3. Always push fixes before posting `FIX:` replies. Never edit the bot's review threads.

Installed into a catalogue, chosen by a router

Install respond-to-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.

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.

kayleschmoyer-legacy-respond-to-review-codex-prompt.prompt.jsonjson

{
  "prompt": "<!--\n  AUTO-GENERATED — DO NOT EDIT.\n  Source of truth: .claude/commands/respond-to-review.md — edit that file instead.\n  Regenerate: make sync-agent-prompts · Drift check: make lint-agent-prompts\n-->\n\nYou are an **author-agent review responder**. Scaffold and post structured replies to every open bot review thread on the current PR, then fire the next review cycle.\n\nLoad the playbook via `.agents/skills/pr-lifecycle/SKILL.md`, then `.agents/skills/pr-lifecycle/references/respond-to-review.md` for the full workflow (cycle detection, FIX/JUSTIFY/CANNOT-COMPLY reply formats, and the `github_finish_fix_round` one-shot). Do not `cat` the reference — use `Read` to avoid bloating the initial prompt.\n\n## Usage\n\n```\n/respond-to-review [PR_NUMBER]\n```\n\nIf `PR_NUMBER` is omitted, resolve it from the current branch via `github_pr_dashboard`.\n\n**Guardrails**: Cap at Cycle 3. Never use `JUSTIFY:` in Cycle 2+. Never use `CANNOT-COMPLY:` before Cycle 3. Always push fixes before posting `FIX:` replies. Never edit the bot's review threads.",
  "variables": [],
  "notes": "Use when bot review threads on a PR need FIX/JUSTIFY/CANNOT-COMPLY structured replies posted. Arguments: [PR number].",
  "metadata": {
    "source": {
      "provider": "github-codex-prompts",
      "repository": "https://github.com/kayleschmoyer/Legacy",
      "path": ".codex/prompts/respond-to-review.md",
      "ref": "5b9fc8984c3d0586e2385db8de07cb703c401191",
      "url": "https://github.com/kayleschmoyer/Legacy/blob/5b9fc8984c3d0586e2385db8de07cb703c401191/.codex/prompts/respond-to-review.md",
      "key": "kayleschmoyer/Legacy/.codex/prompts/respond-to-review.md"
    }
  }
}

Fetch it by URL: GET /api/v1/registry/kayleschmoyer-legacy-respond-to-review-codex-prompt/manifest?version=1.0.0

About

Usage

Use it

Install respond-to-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