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-feature-cmd - Prompt - OpenSmartRoute

Name: ship-feature-cmd
Author: mfareedkhan

Prompt file imported from mfareedkhan/spendly (.claude/commands/ship-feature-cmd.md). Copyright stays with the author.

Step 1 — Identify current branch

git branch --show-current

Store this as CURRENT_BRANCH.

Step 2 — Generate commit message

Run:

git diff --staged
git diff
git log main..HEAD --oneline

Read .claude/specs/ to find the spec for the current feature.

Generate a Conventional Commit message:

feat: new feature
fix: bug fix
chore: config or tooling
docs: documentation only

Rules:

Lowercase
No period at the end
Under 72 characters
Describes what the user can now do, not what the code does

Good: "feat: add delete expense button with confirmation dialog" Bad: "feat: added DELETE route to app.py"

Step 3 — Commit

git add .
git commit -m "<generated-message>"

Report: "✓ Committed — "

Step 4 — Push to feature branch

git push -u origin CURRENT_BRANCH

Report: "✓ Pushed — CURRENT_BRANCH"

Step 5 — Create PR via GitHub MCP

Use the GitHub MCP server to create a pull request from CURRENT_BRANCH into main.

Title: plain English feature name, no conventional commit prefix Example: "Add delete expense functionality"

Description:

## What this PR does
<one paragraph from the spec overview section>

## Changes
<bullet list of every file changed with one line description each>

## Definition of done
<copy the definition of done checklist from the spec,
mark every item as checked [x]>

## How to test
1. Run python app.py
2. Log in as demo@spendly.com / demo123
3. <specific steps from the spec to verify this feature works>

Report: "✓ PR created — "

Step 6 — Merge PR via GitHub MCP

Use the GitHub MCP server to merge the pull request just created. Use squash merge.

Report: "✓ PR merged to main"

Step 7 — Delete remote branch via GitHub MCP

Use the GitHub MCP server to delete CURRENT_BRANCH from GitHub after the merge.

Report: "✓ Remote branch deleted"

Step 8 — Switch to main and pull

git checkout main
git pull origin main

Report: "✓ Switched to main — up to date"

Step 9 — Delete local feature branch

git branch -D CURRENT_BRANCH

Report: "✓ Local branch deleted"

Final summary

Print: ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌ /ship-feature complete ✓ Committed — ✓ Pushed — ✓ PR created and merged ✓ Remote branch deleted ✓ Switched to main ✓ Local branch deleted Next: run /create-spec for the next feature ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

Rules

Never commit directly to main
Always use squash merge
Always delete both remote and local branch after merge
If GitHub MCP is not connected stop and say: "GitHub MCP is not connected. Run /mcp to check connection."
If push fails due to no upstream, use git push -u origin CURRENT_BRANCH
Never proceed to merge if PR creation fails

Install ship-feature-cmd 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.

## Step 1 — Identify current branch ```bash git branch --show-current ``` Store this as CURRENT_BRANCH. ## Step 2 — Generate commit message Run: ```bash git diff --staged git diff git log main..HEAD --oneline ``` Read .claude/specs/ to find the spec for the current feature. Generate a Conventional Commit message: - feat: new feature - fix: bug fix - chore: config or tooling - docs: documentation only Rules: - Lowercase - No period at the end - Under 72 characters - Describes what the user can now do, not what the code does Good: "feat: add delete expense button with confirmation dialog" Bad: "feat: added DELETE route to app.py" ## Step 3 — Commit ```bash git add . git commit -m "<generated-message>" ``` Report: "✓ Committed — <message>" ## Step 4 — Push to feature branch ```bash git push -u origin CURRENT_BRANCH ``` Report: "✓ Pushed — CURRENT_BRANCH" ## Step 5 — Create PR via GitHub MCP Use the GitHub MCP server to create a pull request from CURRENT_BRANCH into main. Title: plain English feature name, no conventional commit prefix Example: "Add delete expense functionality" Description: ```markdown ## What this PR does <one paragraph from the spec overview section> ## Changes <bullet list of every file changed with one line description each> ## Definition of done <copy the definition of done checklist from the spec, mark every item as checked [x]> ## How to test 1. Run python app.py 2. Log in as demo@spendly.com / demo123 3. <specific steps from the spec to verify this feature works> ``` Report: "✓ PR created — <PR URL>" ## Step 6 — Merge PR via GitHub MCP Use the GitHub MCP server to merge the pull request just created. Use squash merge. Report: "✓ PR merged to main" ## Step 7 — Delete remote branch via GitHub MCP Use the GitHub MCP server to delete CURRENT_BRANCH from GitHub after the merge. Report: "✓ Remote branch deleted" ## Step 8 — Switch to main and pull ```bash git checkout main git pull origin main ``` Report: "✓ Switched to main — up to date" ## Step 9 — Delete local feature branch ```bash git branch -D CURRENT_BRANCH ``` Report: "✓ Local branch deleted" ## Final summary Print: ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌ /ship-feature complete ✓ Committed — <message> ✓ Pushed — <branch> ✓ PR created and merged ✓ Remote branch deleted ✓ Switched to main ✓ Local branch deleted Next: run /create-spec for the next feature ╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌ ## Rules - Never commit directly to main - Always use squash merge - Always delete both remote and local branch after merge - If GitHub MCP is not connected stop and say: "GitHub MCP is not connected. Run /mcp to check connection." - If push fails due to no upstream, use git push -u origin CURRENT_BRANCH - Never proceed to merge if PR creation fails

{ "prompt": "## Step 1 — Identify current branch\n```bash\ngit branch --show-current\n```\nStore this as CURRENT_BRANCH.\n\n## Step 2 — Generate commit message\nRun:\n```bash\ngit diff --staged\ngit diff\ngit log main..HEAD --oneline\n```\nRead .claude/specs/ to find the spec for the current feature.\n\nGenerate a Conventional Commit message:\n- feat: new feature\n- fix: bug fix\n- chore: config or tooling\n- docs: documentation only\n\nRules:\n- Lowercase\n- No period at the end\n- Under 72 characters\n- Describes what the user can now do, not what the code does\n\nGood: \"feat: add delete expense button with confirmation dialog\"\nBad: \"feat: added DELETE route to app.py\"\n\n## Step 3 — Commit\n```bash\ngit add .\ngit commit -m \"<generated-message>\"\n```\nReport: \"✓ Committed — <message>\"\n\n## Step 4 — Push to feature branch\n```bash\ngit push -u origin CURRENT_BRANCH\n```\nReport: \"✓ Pushed — CURRENT_BRANCH\"\n\n## Step 5 — Create PR via GitHub MCP\nUse the GitHub MCP server to create a pull request from CURRENT_BRANCH into main.\n\nTitle: plain English feature name, no conventional commit prefix\nExample: \"Add delete expense functionality\"\n\nDescription:\n```markdown\n## What this PR does\n<one paragraph from the spec overview section>\n\n## Changes\n<bullet list of every file changed with one line description each>\n\n## Definition of done\n<copy the definition of done checklist from the spec,\nmark every item as checked [x]>\n\n## How to test\n1. Run python app.py\n2. Log in as demo@spendly.com / demo123\n3. <specific steps from the spec to verify this feature works>\n```\n\nReport: \"✓ PR created — <PR URL>\"\n\n## Step 6 — Merge PR via GitHub MCP\nUse the GitHub MCP server to merge the pull request just created. Use squash merge.\n\nReport: \"✓ PR merged to main\"\n\n## Step 7 — Delete remote branch via GitHub MCP\nUse the GitHub MCP server to delete CURRENT_BRANCH from GitHub after the merge.\n\nReport: \"✓ Remote branch deleted\"\n\n## Step 8 — Switch to main and pull\n```bash\ngit checkout main\ngit pull origin main\n```\nReport: \"✓ Switched to main — up to date\"\n\n## Step 9 — Delete local feature branch\n```bash\ngit branch -D CURRENT_BRANCH\n```\nReport: \"✓ Local branch deleted\"\n\n## Final summary\nPrint:\n╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌\n/ship-feature complete\n✓ Committed — <message>\n✓ Pushed — <branch>\n✓ PR created and merged\n✓ Remote branch deleted\n✓ Switched to main\n✓ Local branch deleted\nNext: run /create-spec for the next feature\n╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌\n\n## Rules\n- Never commit directly to main\n- Always use squash merge\n- Always delete both remote and local branch after merge\n- If GitHub MCP is not connected stop and say:\n \"GitHub MCP is not connected. Run /mcp to check connection.\"\n- If push fails due to no upstream, use git push -u origin CURRENT_BRANCH\n- Never proceed to merge if PR creation fails", "variables": [], "notes": "Commit, push, create PR, merge, and clean up after a feature is complete Tools: Read, Bash, mcp__github__create_pull_request, mcp__github__merge_pull_request, mcp__github__delete_branch.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/mfareedkhan/spendly", "path": ".claude/commands/ship-feature-cmd.md", "ref": "4f0edc13b2dd279ae354c320549001b791434a14", "url": "https://github.com/mfareedkhan/spendly/blob/4f0edc13b2dd279ae354c320549001b791434a14/.claude/commands/ship-feature-cmd.md", "key": "mfareedkhan/spendly/.claude/commands/ship-feature-cmd.md" } } }

ship-feature-cmd

About

Step 1 — Identify current branch

Step 2 — Generate commit message

Step 3 — Commit

Step 4 — Push to feature branch

Step 5 — Create PR via GitHub MCP

Step 6 — Merge PR via GitHub MCP

Step 7 — Delete remote branch via GitHub MCP

Step 8 — Switch to main and pull

Step 9 — Delete local feature branch

Final summary

Rules

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