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.
pr-body-refine - Prompt - OpenSmartRoute
Promptv1.0.0
pr-body-refine
This prompt is retired. Current PR preparation and correction are manager-local through .codex/prompts/pr-body-draft.md and the phase blocker budget.
Prompt file imported from samcantrill/loom (.codex/prompts/pr-body-refine.md). Copyright stays with the author.
Legacy PR Body Refinement
This prompt is retired. Current PR preparation and correction are manager-local
through .codex/prompts/pr-body-draft.md and the phase blocker budget. Do not
create a PR-body artifact or spawn loom_pr_preparer.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# Legacy PR Body Refinement
This prompt is retired. Current PR preparation and correction are manager-local
through .codex/prompts/pr-body-draft.md and the phase blocker budget. Do not
create a PR-body artifact or spawn loom_pr_preparer.
Manifest
The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.
{
"prompt": "# Legacy PR Body Refinement\n\nThis prompt is retired. Current PR preparation and correction are manager-local\nthrough .codex/prompts/pr-body-draft.md and the phase blocker budget. Do not\ncreate a PR-body artifact or spawn loom_pr_preparer.",
"variables": [],
"notes": "This prompt is retired. Current PR preparation and correction are manager-local through .codex/prompts/pr-body-draft.md and the phase blocker budget. Do not create a PR-body artifact or spawn loom_pr_preparer.",
"metadata": {
"source": {
"provider": "github-codex-prompts",
"repository": "https://github.com/samcantrill/loom",
"path": ".codex/prompts/pr-body-refine.md",
"ref": "36c274e78b13a633b9ffae8d3045d69c88ccbbb8",
"url": "https://github.com/samcantrill/loom/blob/36c274e78b13a633b9ffae8d3045d69c88ccbbb8/.codex/prompts/pr-body-refine.md",
"key": "samcantrill/loom/.codex/prompts/pr-body-refine.md"
}
}
}
Installed into a catalogue, chosen by a router
Install pr-body-refine 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.