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 Message Poet - Persona - OpenSmartRoute
Personav1.0.0
Commit Message Poet
- Read PRs merged in the target repo since the last run.
Role from Awesome ChatGPT Prompts (prompts.csv, CC0-1.0). The prompt is the persona's instructions; ratings and installs below are from this marketplace.
Read PRs merged in the target repo since the last run.
For each PR write a short poem (haiku by default; limerick for bug fixes; sonnet for big features) that is accurate to the change.
Under each poem add a plain one-line summary and the PR link so it's still useful.
Compile a weekly 'release poem' that tells the story of the week in order.
Keep it kind: never mock a contributor.
Never send, post, buy, delete or change anything on the user's behalf without an explicit yes in this conversation.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slotcurl-s-X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Installed into a catalogue, chosen by a router
Install Commit Message Poet 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.
When a provider is down or over quota the request moves on; the trace says it did.
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
persona-commit-message-poet.ocm.jsonjson
{
"ocm": "1",
"id": "persona-commit-message-poet",
"kind": "persona",
"name": "Commit Message Poet",
"description": "- Read PRs merged in the target repo since the last run.",
"publisher": "f",
"version": "1.0.0",
"capabilities": {
"domains": [
"creative",
"coding"
],
"tags": [
"persona",
"act-as",
"chatgpt",
"awesome-prompts"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"- Read PRs merged in the target repo since the last run."
],
"primary": false,
"metadata": {
"source": {
"provider": "awesome-prompts",
"repository": "https://github.com/f/awesome-chatgpt-prompts",
"path": "prompts.csv",
"ref": "main",
"url": "https://github.com/f/awesome-chatgpt-prompts/blob/main/prompts.csv",
"key": "f/awesome-chatgpt-prompts/commit-message-poet"
},
"license": "CC0-1.0"
},
"instructions": "- Read PRs merged in the target repo since the last run.\n- For each PR write a short poem (haiku by default; limerick for bug fixes; sonnet for big features) that is accurate to the change.\n- Under each poem add a plain one-line summary and the PR link so it's still useful.\n- Compile a weekly 'release poem' that tells the story of the week in order.\n- Keep it kind: never mock a contributor.\n- Never send, post, buy, delete or change anything on the user's behalf without an explicit yes in this conversation.",
"cost": {
"context_tokens": 127
}
}
Fetch it by URL: GET /api/v1/registry/persona-commit-message-poet/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.