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.

clean-commits - Skill - OpenSmartRoute

Name: clean-commits
Author: whobot-ai

Imported from whobot-ai/skills (skills/clean-commits/SKILL.md). Install upstream with npx skills add whobot-ai/skills --skill clean-commits. Copyright stays with the author.

Clean Commits

帮用户写出只描述改动本身的 commit message：主题行准确、正文讲清动机、零噪音。

输入

已暂存或未暂存的代码改动（自己用 git 命令读取，不需要用户描述）
用户可能附带的上下文（关联 issue、改动动机）；没有就从 diff 推断

工作流

git diff --staged 读实际改动（无暂存内容则看 git diff）
git log --oneline -15 观察仓库既有风格：是否用 Conventional Commits 前缀（feat:/fix:…）、中文还是英文——跟随既有风格，不要另起一套
从改动的效果（而非代码机制）提炼主题行
动机不明显时补正文，说明为什么改，而不是复述 diff
若暂存区混入多个不相关改动，先建议拆分再提交

输出格式

主题行：祈使语气，≤ 72 字符，无句号
正文（可选）：与主题行空一行，每行 ≤ 72 字符，只写动机与取舍
禁止出现：
- Co-Authored-By: 等 AI 共同作者署名
- 🤖 Generated with ... 等任何工具水印
- 仓库没在用的 issue 标签、emoji 前缀等额外噪音

示例：

fix: 配置缺 timeout 字段时回退默认值

v0.3 写出的配置文件完全没有 timeout 键，加载时直接崩溃。
改为缺键时应用默认值，而不是假设键一定存在。

add retry with backoff to webhook delivery

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://osr-api.kindrock-caaab1a2.centralindia.azurecontainerapps.io/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

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

{ "ocm": "1", "id": "whobot-ai-skills-clean-commits", "kind": "skill", "name": "clean-commits", "description": "生成干净、符合仓库既有风格的 git commit message。当用户要提交代码、让你写/改 commit message、拆分提交，或要求提交历史保持干净时使用。只写改动本身——不加 AI 共同作者署名，不加任何生成工具水印。", "publisher": "whobot-ai", "version": "1.0.0", "capabilities": { "domains": [ "coding", "customer_support" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "生成干净、符合仓库既有风格的 git commit message。当用户要提交代码、让你写/改 commit message、拆分提交，或要求提交历史保持干净时使用。只写改动本身——不加 AI 共同作者署名，不加任何生成工具水印。" ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/whobot-ai/skills", "path": "skills/clean-commits/SKILL.md", "ref": "HEAD", "url": "https://github.com/whobot-ai/skills/blob/HEAD/skills/clean-commits/SKILL.md", "key": "whobot-ai/skills/skills/clean-commits/SKILL.md" } }, "instructions": "# Clean Commits\n\n帮用户写出只描述改动本身的 commit message：主题行准确、正文讲清动机、零噪音。\n\n## 输入\n\n- 已暂存或未暂存的代码改动（自己用 git 命令读取，不需要用户描述）\n- 用户可能附带的上下文（关联 issue、改动动机）；没有就从 diff 推断\n\n## 工作流\n\n1. `git diff --staged` 读实际改动（无暂存内容则看 `git diff`）\n2. `git log --oneline -15` 观察仓库既有风格：是否用 Conventional Commits\n 前缀（`feat:`/`fix:`…）、中文还是英文——**跟随既有风格，不要另起一套**\n3. 从改动的*效果*（而非代码机制）提炼主题行\n4. 动机不明显时补正文，说明*为什么*改，而不是复述 diff\n5. 若暂存区混入多个不相关改动，先建议拆分再提交\n\n## 输出格式\n\n- 主题行：祈使语气，≤ 72 字符，无句号\n- 正文（可选）：与主题行空一行，每行 ≤ 72 字符，只写动机与取舍\n- **禁止出现**：\n - `Co-Authored-By:` 等 AI 共同作者署名\n - `🤖 Generated with ...` 等任何工具水印\n - 仓库没在用的 issue 标签、emoji 前缀等额外噪音\n\n示例：\n\n```\nfix:", "cost": { "context_tokens": 184 } }

clean-commits

About

Clean Commits

输入

工作流

输出格式

Use it

Install clean-commits 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