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.

release-notes - Prompt - OpenSmartRoute

Name: release-notes
Author: NikoMix

Prompt file imported from NikoMix/microhack-agentic-devops (.github/prompts/release-notes.prompt.md). Fill in {{range}} before use. Copyright stays with the author.

Draft release notes

Act as the Release Notes agent. Draft release notes for {{range}}.

Steps:

Use the read-only github tools to list the pull requests merged in range (number, title, author, labels, merge date).
Group each PR into exactly one category — ✨ Features, 🐛 Fixes, 🔒 Security, 📖 Docs, 🏗️ Infrastructure, 🧹 Maintenance — driven by its area:* / workstream:* labels, falling back to the title. A security fix always lands under Security.
Write one verb-first bullet per PR (≤ ~120 chars) ending in (#number), and lead with a short plain-language highlights paragraph.
Never fabricate PRs, numbers, authors, or changes. If the range is empty, return a skeleton noting "No merged pull requests in range."

Output Markdown ready to paste into a GitHub Release body. Draft only — tagging and publishing stay with the agentic-release-notes.yml workflow and a human maintainer.

# Draft release notes Act as the [Release Notes agent](../agents/release-notes.agent.md). Draft release notes for {{range}}. Steps: 1. Use the read-only `github` tools to list the pull requests merged in range (number, title, author, labels, merge date). 2. Group each PR into exactly one category — ✨ Features, 🐛 Fixes, 🔒 Security, 📖 Docs, 🏗️ Infrastructure, 🧹 Maintenance — driven by its `area:*` / `workstream:*` labels, falling back to the title. A security fix always lands under **Security**. 3. Write one verb-first bullet per PR (≤ ~120 chars) ending in `(#number)`, and lead with a short plain-language **highlights** paragraph. 4. Never fabricate PRs, numbers, authors, or changes. If the range is empty, return a skeleton noting "No merged pull requests in range." Output Markdown ready to paste into a GitHub Release body. Draft only — tagging and publishing stay with the `agentic-release-notes.yml` workflow and a human maintainer.

Install release-notes 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": "# Draft release notes\n\nAct as the [Release Notes agent](../agents/release-notes.agent.md). Draft release notes for\n{{range}}.\n\nSteps:\n\n1. Use the read-only `github` tools to list the pull requests merged in range (number, title, author,\n labels, merge date).\n2. Group each PR into exactly one category — ✨ Features, 🐛 Fixes, 🔒 Security, 📖 Docs,\n 🏗️ Infrastructure, 🧹 Maintenance — driven by its `area:*` / `workstream:*` labels, falling back to the\n title. A security fix always lands under **Security**.\n3. Write one verb-first bullet per PR (≤ ~120 chars) ending in `(#number)`, and lead with a short\n plain-language **highlights** paragraph.\n4. Never fabricate PRs, numbers, authors, or changes. If the range is empty, return a skeleton noting\n \"No merged pull requests in range.\"\n\nOutput Markdown ready to paste into a GitHub Release body. Draft only — tagging and publishing stay with\nthe `agentic-release-notes.yml` workflow and a human maintainer.", "variables": [ "range" ], "notes": "Draft Markdown release notes from the pull requests merged since the last release. Tools: read, search, github/*. Arguments: [previous tag] [target tag].", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/NikoMix/microhack-agentic-devops", "path": ".github/prompts/release-notes.prompt.md", "ref": "3557c28286af3b529bcee09974b032b600bc4297", "url": "https://github.com/NikoMix/microhack-agentic-devops/blob/3557c28286af3b529bcee09974b032b600bc4297/.github/prompts/release-notes.prompt.md", "key": "NikoMix/microhack-agentic-devops/.github/prompts/release-notes.prompt.md" } } }

release-notes

About

Draft release notes

Use it

Install release-notes 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