Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
commit - Prompt - OpenSmartRoute
Promptv1.0.0
commit
Commit ALL our changes so far. Make sure you take into account folders starting with a dot (e.g., .serena/, .claude/). Break down the changes into smaller commits if you feel it's necessary.
Prompt file imported from w00ing/config.tmux (.codex/prompts/commit.md). Copyright stays with the author.
Commit ALL our changes so far.
Make sure you take into account folders starting with a dot (e.g., .serena/, .claude/).
Break down the changes into smaller commits if you feel it's necessary.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
Commit ALL our changes so far.
Make sure you take into account folders starting with a dot (e.g., `.serena/`, `.claude/`).
Break down the changes into smaller commits if you feel it's necessary.
Manifest
The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.
{
"prompt": "Commit ALL our changes so far.\nMake sure you take into account folders starting with a dot (e.g., `.serena/`, `.claude/`).\nBreak down the changes into smaller commits if you feel it's necessary.",
"variables": [],
"notes": "Commit ALL our changes so far. Make sure you take into account folders starting with a dot (e.g., `.serena/`, `.claude/`). Break down the changes into smaller commits if you feel it's necessary.",
"metadata": {
"source": {
"provider": "github-codex-prompts",
"repository": "https://github.com/w00ing/config.tmux",
"path": ".codex/prompts/commit.md",
"ref": "c7b0bffbe05a3be8469ed9f932fff1abd07c2723",
"url": "https://github.com/w00ing/config.tmux/blob/c7b0bffbe05a3be8469ed9f932fff1abd07c2723/.codex/prompts/commit.md",
"key": "w00ing/config.tmux/.codex/prompts/commit.md"
}
}
}
Installed into a catalogue, chosen by a router
Install commit 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.