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.
get-pr-comments - Skill - OpenSmartRoute
Skillv1.0.0
get-pr-comments
Fetch and summarize review comments from the active pull request
Imported from Velclaw/OCodejs (.qwen/skills/get-pr-comments/SKILL.md). Install upstream with npx skills add Velclaw/OCodejs --skill get-pr-comments. Copyright stays with the author.
Get PR comments
Trigger
Need a concise, actionable summary of feedback on the active pull request.
Workflow
Resolve the active PR for the current branch.
Fetch review comments and discussion comments.
Group feedback by severity and actionability.
Return a concise action list.
Output
Grouped feedback summary
Action list ordered by priority
Open questions that still need clarification
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 get-pr-comments 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.
velclaw-ocodejs-get-pr-comments.ocm.jsonjson
{
"ocm": "1",
"id": "velclaw-ocodejs-get-pr-comments",
"kind": "skill",
"name": "get-pr-comments",
"description": "Fetch and summarize review comments from the active pull request",
"publisher": "Velclaw",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Fetch and summarize review comments from the active pull request"
],
"primary": false,
"metadata": {
"source": {
"provider": "github",
"repository": "https://github.com/Velclaw/OCodejs",
"path": ".qwen/skills/get-pr-comments/SKILL.md",
"ref": "526665baae84ae04e49cfe7f15fb6e666498493a",
"url": "https://github.com/Velclaw/OCodejs/blob/526665baae84ae04e49cfe7f15fb6e666498493a/.qwen/skills/get-pr-comments/SKILL.md",
"key": "Velclaw/OCodejs/.qwen/skills/get-pr-comments/SKILL.md"
}
},
"instructions": "# Get PR comments\n\n## Trigger\n\nNeed a concise, actionable summary of feedback on the active pull request.\n\n## Workflow\n\n1. Resolve the active PR for the current branch.\n2. Fetch review comments and discussion comments.\n3. Group feedback by severity and actionability.\n4. Return a concise action list.\n\n## Output\n\n- Grouped feedback summary\n- Action list ordered by priority\n- Open questions that still need clarification",
"cost": {
"context_tokens": 105
}
}
Fetch it by URL: GET /api/v1/registry/velclaw-ocodejs-get-pr-comments/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.