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.
gh-address-comments - Skill - OpenSmartRoute
Skillv1.0.0
gh-address-comments
Address review and issue comments on the open GitHub PR for the current branch using gh CLI. Use when user says "address PR comments", "fix review feedback", "respond to PR review", or "handle PR…
Imported from tech-leads-club/agent-skills (packages/skills-catalog/skills/(development)/gh-address-comments/SKILL.md). Install upstream with npx skills add tech-leads-club/agent-skills --skill gh-address-comments. Copyright stays with the author.
PR Comment Handler
Guide to find the open PR for the current branch and address its comments with gh CLI.
Prerequisites: Ensure gh is authenticated before running commands. Check authentication status with gh auth status. If not authenticated, instruct the user to run gh auth login to authenticate with GitHub.
1) Inspect comments needing attention
Run scripts/fetch_comments.py which will print out all the comments and review threads on the PR
2) Ask the user for clarification
Number all the review threads and comments and provide a short summary of what would be required to apply a fix for it
Ask the user which numbered comments should be addressed
3) If user chooses comments
Apply fixes for the selected comments
Notes:
If gh hits auth/rate issues mid-run, prompt the user to re-authenticate with gh auth login, then retry.
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 gh-address-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.
{
"ocm": "1",
"id": "tech-leads-club-agent-skills-gh-address-comments",
"kind": "skill",
"name": "gh-address-comments",
"description": "Address review and issue comments on the open GitHub PR for the current branch using gh CLI. Use when user says \"address PR comments\", \"fix review feedback\", \"respond to PR review\", or \"handle PR comments\". Verifies gh auth first and prompts to authenticate if not logged in. Do NOT use for creating PRs, CI debugging (use gh-fix-ci), or general Git operations.",
"publisher": "tech-leads-club",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"skills-sh"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Address review and issue comments on the open GitHub PR for the current branch using gh CLI. Use when user says \"address PR comments\", \"fix review feedback\", \"respond to PR review\", or \"handle PR comments\". Verifies gh auth first and prompts to authenticate if not logged in. Do NOT use for creating PRs, CI debugging (use gh-fix-ci), or general Git operations."
],
"primary": false,
"metadata": {
"source": {
"provider": "skills.sh",
"repository": "https://github.com/tech-leads-club/agent-skills",
"path": "packages/skills-catalog/skills/(development)/gh-address-comments/SKILL.md",
"ref": "HEAD",
"url": "https://github.com/tech-leads-club/agent-skills/blob/HEAD/packages/skills-catalog/skills/(development)/gh-address-comments/SKILL.md",
"key": "tech-leads-club/agent-skills/packages/skills-catalog/skills/(development)/gh-address-comments/SKILL.md"
}
},
"instructions": "# PR Comment Handler\n\nGuide to find the open PR for the current branch and address its comments with gh CLI.\n\n**Prerequisites:** Ensure `gh` is authenticated before running commands. Check authentication status with `gh auth status`. If not authenticated, instruct the user to run `gh auth login` to authenticate with GitHub.\n\n## 1) Inspect comments needing attention\n\n- Run scripts/fetch_comments.py which will print out all the comments and review threads on the PR\n\n## 2) Ask the user for clarification\n\n- Number all the review threads and comments and provide a short summary of what would be required to apply a fix for it\n- Ask the user which numbered comments should be addressed\n\n## 3) If user chooses comments\n\n- Apply fixes for the selected comments\n\nNotes:\n\n- If gh hits auth/rate issues mid-run, prompt the user to re-authenticate with `gh auth login`, then retry.",
"cost": {
"context_tokens": 219
}
}
Fetch it by URL: GET /api/v1/registry/tech-leads-club-agent-skills-gh-address-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.