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.

sync-docs - Prompt - OpenSmartRoute

Name: sync-docs
Author: Leasarr

Prompt file imported from Leasarr/leasarr-app (.claude/commands/sync-docs.md). Copyright stays with the author.

Scan recent git commits and update Leasarr docs to reflect the current state of the app.

What this command does

Finds the last commit that touched a doc file (.claude/rules/, documents/progress/, or documents/mvp-launch-roadmap/).
Lists all feature/fix/feat commits since that commit.
For each commit that represents a meaningful change (skip pure chore/fix commits that don't change app behaviour), determines what doc entries it needs.
Updates the relevant docs.

Step-by-step

Step 1 — Find the baseline

git log --oneline --diff-filter=M -- '.claude/rules/*.md' 'documents/progress/*.md' 'documents/mvp-launch-roadmap/*.md' | head -1

This gives the most recent docs-update commit. Note its hash.

Step 2 — List commits since then

git log --oneline <hash>..HEAD

Step 3 — For each commit that added a feature or fixed a meaningful bug:

Read its diff (git show <hash> --stat) to understand what changed.
Map it to one of these doc targets:

What changed	Update here
New route, API route, or migration	`.claude/rules/architecture.md` — add to the appropriate table
New key file or hook	`.claude/rules/architecture.md` — add to Key files
Auth or middleware behaviour	`.claude/rules/auth.md`
New component or convention	`.claude/rules/conventions.md`
Any shipped feature	`documents/progress/progress_table.md` — add a row
Any shipped feature	`documents/progress/roadmap.md` — add a row to the progress table and the Gantt if it represents a new phase
Blocking item now resolved	`documents/mvp-launch-roadmap/leasarr-mvp-launch-roadmap.md` — mark as done in "Remaining Before Launch"

Step 4 — Write the updates

In progress tables: add rows with format | **Phase** | Description | Date |. Keep descriptions concise (one line).
In architecture.md tables: match the existing row format exactly.
In the mvp-launch-roadmap: bump the version number (increment by 1) and today's date, and add a one-line entry to the Document Control table.
Do NOT rewrite or restructure existing content — only append or mark items done.
Do NOT add entries for pure bug fixes, chore commits, or typo fixes unless they fix a security issue.

Step 5 — Report Tell the user:

How many commits were scanned.
Which docs were updated and what was added.
Any commits you skipped and why.
Whether any "Remaining Before Launch" items are now done.

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

Scan recent git commits and update Leasarr docs to reflect the current state of the app. ## What this command does 1. Finds the last commit that touched a doc file (`.claude/rules/`, `documents/progress/`, or `documents/mvp-launch-roadmap/`). 2. Lists all feature/fix/feat commits since that commit. 3. For each commit that represents a meaningful change (skip pure chore/fix commits that don't change app behaviour), determines what doc entries it needs. 4. Updates the relevant docs. ## Step-by-step **Step 1 — Find the baseline** ```bash git log --oneline --diff-filter=M -- '.claude/rules/*.md' 'documents/progress/*.md' 'documents/mvp-launch-roadmap/*.md' | head -1 ``` This gives the most recent docs-update commit. Note its hash. **Step 2 — List commits since then** ```bash git log --oneline <hash>..HEAD ``` **Step 3 — For each commit that added a feature or fixed a meaningful bug:** - Read its diff (`git show <hash> --stat`) to understand what changed. - Map it to one of these doc targets: | What changed | Update here | |---|---| | New route, API route, or migration | `.claude/rules/architecture.md` — add to the appropriate table | | New key file or hook | `.claude/rules/architecture.md` — add to Key files | | Auth or middleware behaviour | `.claude/rules/auth.md` | | New component or convention | `.claude/rules/conventions.md` | | Any shipped feature | `documents/progress/progress_table.md` — add a row | | Any shipped feature | `documents/progress/roadmap.md` — add a row to the progress table and the Gantt if it represents a new phase | | Blocking item now resolved | `documents/mvp-launch-roadmap/leasarr-mvp-launch-roadmap.md` — mark as done in "Remaining Before Launch" | **Step 4 — Write the updates** - In progress tables: add rows with format `| **Phase** | Description | Date |`. Keep descriptions concise (one line). - In architecture.md tables: match the existing row format exactly. - In the mvp-launch-roadmap: bump the version number (increment by 1) and today's date, and add a one-line entry to the Document Control table. - Do NOT rewrite or restructure existing content — only append or mark items done. - Do NOT add entries for pure bug fixes, chore commits, or typo fixes unless they fix a security issue. **Step 5 — Report** Tell the user: - How many commits were scanned. - Which docs were updated and what was added. - Any commits you skipped and why. - Whether any "Remaining Before Launch" items are now done.

{ "prompt": "Scan recent git commits and update Leasarr docs to reflect the current state of the app.\n\n## What this command does\n\n1. Finds the last commit that touched a doc file (`.claude/rules/`, `documents/progress/`, or `documents/mvp-launch-roadmap/`).\n2. Lists all feature/fix/feat commits since that commit.\n3. For each commit that represents a meaningful change (skip pure chore/fix commits that don't change app behaviour), determines what doc entries it needs.\n4. Updates the relevant docs.\n\n## Step-by-step\n\n**Step 1 — Find the baseline**\n```bash\ngit log --oneline --diff-filter=M -- '.claude/rules/*.md' 'documents/progress/*.md' 'documents/mvp-launch-roadmap/*.md' | head -1\n```\nThis gives the most recent docs-update commit. Note its hash.\n\n**Step 2 — List commits since then**\n```bash\ngit log --oneline <hash>..HEAD\n```\n\n**Step 3 — For each commit that added a feature or fixed a meaningful bug:**\n- Read its diff (`git show <hash> --stat`) to understand what changed.\n- Map it to one of these doc targets:\n\n| What changed | Update here |\n|---|---|\n| New route, API route, or migration | `.claude/rules/architecture.md` — add to the appropriate table |\n| New key file or hook | `.claude/rules/architecture.md` — add to Key files |\n| Auth or middleware behaviour | `.claude/rules/auth.md` |\n| New component or convention | `.claude/rules/conventions.md` |\n| Any shipped feature | `documents/progress/progress_table.md` — add a row |\n| Any shipped feature | `documents/progress/roadmap.md` — add a row to the progress table and the Gantt if it represents a new phase |\n| Blocking item now resolved | `documents/mvp-launch-roadmap/leasarr-mvp-launch-roadmap.md` — mark as done in \"Remaining Before Launch\" |\n\n**Step 4 — Write the updates**\n- In progress tables: add rows with format `| **Phase** | Description | Date |`. Keep descriptions concise (one line).\n- In architecture.md tables: match the existing row format exactly.\n- In the mvp-launch-roadmap: bump the version number (increment by 1) and today's date, and add a one-line entry to the Document Control table.\n- Do NOT rewrite or restructure existing content — only append or mark items done.\n- Do NOT add entries for pure bug fixes, chore commits, or typo fixes unless they fix a security issue.\n\n**Step 5 — Report**\nTell the user:\n- How many commits were scanned.\n- Which docs were updated and what was added.\n- Any commits you skipped and why.\n- Whether any \"Remaining Before Launch\" items are now done.", "variables": [], "notes": "Scan recent git commits and update Leasarr docs to reflect the current state of the app.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/Leasarr/leasarr-app", "path": ".claude/commands/sync-docs.md", "ref": "bf6b7b94cc312e4beb5a6a1c963370336e2b7106", "url": "https://github.com/Leasarr/leasarr-app/blob/bf6b7b94cc312e4beb5a6a1c963370336e2b7106/.claude/commands/sync-docs.md", "key": "Leasarr/leasarr-app/.claude/commands/sync-docs.md" } } }

sync-docs

About

What this command does

Step-by-step

Install sync-docs 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