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.

ship - Prompt - OpenSmartRoute

Name: ship
Author: I7T5

Prompt file imported from I7T5/Edmund (.claude/commands/ship.md). Fill in {{arguments}} before use. Copyright stays with the author.

Ship the current uncommitted changes in this repo as a self-merging PR. The change is described as: {{arguments}}

Run all git/gh commands from the repository root. Follow these steps exactly, stopping and reporting if any step fails:

Survey. git status --short and git diff --stat. Confirm there are changes to ship. If {{arguments}} is empty, infer a concise description from the diff.
Test first (project rule). Run swift test. If anything fails, stop and show the failure — do not commit.
Branch. If currently on main, create a topic branch named fix/…, feature/…, ci/…, or chore/… as fits the change (kebab-case, derived from the description). If already on a non-main branch, reuse it.
Commit. Stage only the files that belong to this change (surgical — no unrelated files). Write a commit message: a concise imperative subject line and a body explaining the why. No attribution trailer. Keep it one logical change per commit.
Push. git push -u origin <branch>.
Open the PR. gh pr create with a title matching the subject and a body that explains what and why. No generated-by / attribution footer.
Auto-merge. gh pr merge <#> --auto --merge --delete-branch. Branch protection requires the test check, so this queues the PR to merge itself the moment CI passes — no manual merge needed.
Report. Print the PR URL and state that it will merge automatically when CI is green. Do not sit and poll CI unless asked.

Never force-push, never touch main directly, and never bypass the failing-test stop in step 2.

Install ship 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": "Ship the current uncommitted changes in this repo as a self-merging PR. The\nchange is described as: **{{arguments}}**\n\nRun all git/gh commands from the repository root. Follow these steps exactly,\nstopping and reporting if any step fails:\n\n1. **Survey.** `git status --short` and `git diff --stat`. Confirm there are\n changes to ship. If `{{arguments}}` is empty, infer a concise description from\n the diff.\n\n2. **Test first (project rule).** Run `swift test`. If anything fails, stop and\n show the failure — do not commit.\n\n3. **Branch.** If currently on `main`, create a topic branch named\n `fix/…`, `feature/…`, `ci/…`, or `chore/…` as fits the change (kebab-case,\n derived from the description). If already on a non-main branch, reuse it.\n\n4. **Commit.** Stage only the files that belong to this change (surgical — no\n unrelated files). Write a commit message: a concise imperative subject line\n and a body explaining the *why*. No attribution trailer.\n Keep it one logical change per commit.\n\n5. **Push.** `git push -u origin <branch>`.\n\n6. **Open the PR.** `gh pr create` with a title matching the subject and a body\n that explains what and why. No generated-by / attribution footer.\n\n7. **Auto-merge.** `gh pr merge <#> --auto --merge --delete-branch`. Branch\n protection requires the `test` check, so this queues the PR to merge itself\n the moment CI passes — no manual merge needed.\n\n8. **Report.** Print the PR URL and state that it will merge automatically when\n CI is green. Do **not** sit and poll CI unless asked.\n\nNever force-push, never touch `main` directly, and never bypass the failing-test\nstop in step 2.", "variables": [ "arguments" ], "notes": "Branch, test, commit, push, open a PR, and enable auto-merge for the current working-tree changes Tools: Bash, Read, Edit. Arguments: [short description of the change].", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/I7T5/Edmund", "path": ".claude/commands/ship.md", "ref": "10244bd8d7591e80ae8f72252c008b1b6252d89b", "url": "https://github.com/I7T5/Edmund/blob/10244bd8d7591e80ae8f72252c008b1b6252d89b/.claude/commands/ship.md", "key": "I7T5/Edmund/.claude/commands/ship.md" } } }

ship

About

Use it

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