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.

pr - Prompt - OpenSmartRoute

Name: pr
Author: mad-core

Prompt file imported from mad-core/mad-edge (.claude/commands/pr.md). Fill in {{arguments}} before use. Copyright stays with the author.

Create a pull request for the current branch. Follow the steps in order.

Step 1 — Identify the related issue

If {{arguments}} contains an issue number, use it. Otherwise try to infer it from the branch name (pattern: <type>/<number>-<slug>).

If no issue number can be inferred and --auto is not set, use AskUserQuestion:

"Which issue does this PR close? (Enter number, or 'none')"

Store as {issue_number} (may be empty).

Step 2 — Collect context

git branch --show-current
git log main..HEAD --oneline

Store the current branch as {branch} and the commit list as {commits}.

If {branch} is main or the default branch, stop and report: "Cannot open a PR from the default branch."

Step 3 — Determine base branch

Infer base from the branch name prefix or the commit log origin. Default to main.

Use AskUserQuestion to confirm:

"Base branch: main. Confirm or change?" Options: Confirm / Other (specify)

Store as {base_branch}.

Step 4 — Build PR title and body

Derive the PR title from the most significant commit subject, following Conventional Commits style (≤72 chars).

Build the body:

## Summary
<1–3 bullet points: what changed and why, derived from {commits}>

## Related issue
Closes #{issue_number}
(omit this section if issue_number is empty)

## Type of change
- [ ] bug fix
- [ ] feature
- [ ] refactor
- [ ] ci / tooling
- [ ] chore / docs

## Test plan
- [ ] <key scenario>
- [ ] <edge case>

🤖 Generated with [Claude Code](https://claude.ai/claude-code)

Check the correct "Type of change" box based on the branch prefix or commit types.

Step 5 — Confirm and create

Use AskUserQuestion to show the full draft:

"Ready to open PR:\n\nTitle: \nBase: {base_branch}\n\n\n\nProceed?" Options: Create PR / Edit title / Edit body / Cancel

If "Edit title" or "Edit body": collect the correction via AskUserQuestion, apply it, re-present. Repeat until confirmed or cancelled.

Once confirmed:

gh pr create \
  --base {base_branch} \
  --title "<title>" \
  --body "<body>"

Report the PR URL to the user.

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

Create a pull request for the current branch. Follow the steps in order. --- ## Step 1 — Identify the related issue If `{{arguments}}` contains an issue number, use it. Otherwise try to infer it from the branch name (pattern: `<type>/<number>-<slug>`). If no issue number can be inferred and `--auto` is not set, use `AskUserQuestion`: > "Which issue does this PR close? (Enter number, or 'none')" Store as `{issue_number}` (may be empty). --- ## Step 2 — Collect context ```bash git branch --show-current git log main..HEAD --oneline ``` Store the current branch as `{branch}` and the commit list as `{commits}`. If `{branch}` is `main` or the default branch, stop and report: "Cannot open a PR from the default branch." --- ## Step 3 — Determine base branch Infer base from the branch name prefix or the commit log origin. Default to `main`. Use `AskUserQuestion` to confirm: > "Base branch: `main`. Confirm or change?" > Options: Confirm / Other (specify) Store as `{base_branch}`. --- ## Step 4 — Build PR title and body Derive the PR title from the most significant commit subject, following Conventional Commits style (≤72 chars). Build the body: ```markdown ## Summary <1–3 bullet points: what changed and why, derived from {commits}> ## Related issue Closes #{issue_number} (omit this section if issue_number is empty) ## Type of change - [ ] bug fix - [ ] feature - [ ] refactor - [ ] ci / tooling - [ ] chore / docs ## Test plan - [ ] <key scenario> - [ ] <edge case> 🤖 Generated with [Claude Code](https://claude.ai/claude-code) ``` Check the correct "Type of change" box based on the branch prefix or commit types. --- ## Step 5 — Confirm and create Use `AskUserQuestion` to show the full draft: > "Ready to open PR:\n\nTitle: <title>\nBase: {base_branch}\n\n<body>\n\nProceed?" > Options: Create PR / Edit title / Edit body / Cancel If "Edit title" or "Edit body": collect the correction via `AskUserQuestion`, apply it, re-present. Repeat until confirmed or cancelled. Once confirmed: ```bash gh pr create \ --base {base_branch} \ --title "<title>" \ --body "<body>" ``` Report the PR URL to the user.

{ "prompt": "Create a pull request for the current branch. Follow the steps in order.\n\n---\n\n## Step 1 — Identify the related issue\n\nIf `{{arguments}}` contains an issue number, use it. Otherwise try to infer it from the branch name (pattern: `<type>/<number>-<slug>`).\n\nIf no issue number can be inferred and `--auto` is not set, use `AskUserQuestion`:\n\n> \"Which issue does this PR close? (Enter number, or 'none')\"\n\nStore as `{issue_number}` (may be empty).\n\n---\n\n## Step 2 — Collect context\n\n```bash\ngit branch --show-current\ngit log main..HEAD --oneline\n```\n\nStore the current branch as `{branch}` and the commit list as `{commits}`.\n\nIf `{branch}` is `main` or the default branch, stop and report: \"Cannot open a PR from the default branch.\"\n\n---\n\n## Step 3 — Determine base branch\n\nInfer base from the branch name prefix or the commit log origin. Default to `main`.\n\nUse `AskUserQuestion` to confirm:\n\n> \"Base branch: `main`. Confirm or change?\"\n> Options: Confirm / Other (specify)\n\nStore as `{base_branch}`.\n\n---\n\n## Step 4 — Build PR title and body\n\nDerive the PR title from the most significant commit subject, following Conventional Commits style (≤72 chars).\n\nBuild the body:\n\n```markdown\n## Summary\n<1–3 bullet points: what changed and why, derived from {commits}>\n\n## Related issue\nCloses #{issue_number}\n(omit this section if issue_number is empty)\n\n## Type of change\n- [ ] bug fix\n- [ ] feature\n- [ ] refactor\n- [ ] ci / tooling\n- [ ] chore / docs\n\n## Test plan\n- [ ] <key scenario>\n- [ ] <edge case>\n\n🤖 Generated with [Claude Code](https://claude.ai/claude-code)\n```\n\nCheck the correct \"Type of change\" box based on the branch prefix or commit types.\n\n---\n\n## Step 5 — Confirm and create\n\nUse `AskUserQuestion` to show the full draft:\n\n> \"Ready to open PR:\\n\\nTitle: <title>\\nBase: {base_branch}\\n\\n<body>\\n\\nProceed?\"\n> Options: Create PR / Edit title / Edit body / Cancel\n\nIf \"Edit title\" or \"Edit body\": collect the correction via `AskUserQuestion`, apply it, re-present. Repeat until confirmed or cancelled.\n\nOnce confirmed:\n\n```bash\ngh pr create \\\n --base {base_branch} \\\n --title \"<title>\" \\\n --body \"<body>\"\n```\n\nReport the PR URL to the user.", "variables": [ "arguments" ], "notes": "Open a pull request for the current branch. Infers the related issue from branch name or asks. Always uses AskUserQuestion before creating. Arguments: [issue-number or --auto].", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/mad-core/mad-edge", "path": ".claude/commands/pr.md", "ref": "e2484a5e247502d8fba26b1435bef0027f693238", "url": "https://github.com/mad-core/mad-edge/blob/e2484a5e247502d8fba26b1435bef0027f693238/.claude/commands/pr.md", "key": "mad-core/mad-edge/.claude/commands/pr.md" } } }

pr

About

Step 1 — Identify the related issue

Step 2 — Collect context

Step 3 — Determine base branch

Step 4 — Build PR title and body

Step 5 — Confirm and create

Install 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

Use it

Manifest

Reviews