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.
new-branch-and-pr - Skill - OpenSmartRoute
Skillv1.0.0
new-branch-and-pr
Create a fresh branch, complete work, and open a pull request
Imported from Velclaw/OCodejs (.goose/skills/new-branch-and-pr/SKILL.md). Install upstream with npx skills add Velclaw/OCodejs --skill new-branch-and-pr. Copyright stays with the author.
New branch and PR
Trigger
Starting work that should be shipped through a clean branch and pull request workflow.
Workflow
Ensure the working tree is clean or explicitly handled.
Create a descriptive branch from the latest main.
Complete implementation and tests.
Commit focused changes and push.
Create a concise PR with summary and test notes.
Guardrails
Keep branch scope focused on one change set.
Include verification notes before requesting review.
Output
New branch name
PR summary and test notes
PR URL
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 new-branch-and-pr 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-new-branch-and-pr.ocm.jsonjson
{
"ocm": "1",
"id": "velclaw-ocodejs-new-branch-and-pr",
"kind": "skill",
"name": "new-branch-and-pr",
"description": "Create a fresh branch, complete work, and open a pull request",
"publisher": "Velclaw",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Create a fresh branch, complete work, and open a pull request"
],
"primary": false,
"metadata": {
"source": {
"provider": "github",
"repository": "https://github.com/Velclaw/OCodejs",
"path": ".goose/skills/new-branch-and-pr/SKILL.md",
"ref": "526665baae84ae04e49cfe7f15fb6e666498493a",
"url": "https://github.com/Velclaw/OCodejs/blob/526665baae84ae04e49cfe7f15fb6e666498493a/.goose/skills/new-branch-and-pr/SKILL.md",
"key": "Velclaw/OCodejs/.goose/skills/new-branch-and-pr/SKILL.md"
}
},
"instructions": "# New branch and PR\n\n## Trigger\n\nStarting work that should be shipped through a clean branch and pull request workflow.\n\n## Workflow\n\n1. Ensure the working tree is clean or explicitly handled.\n2. Create a descriptive branch from the latest main.\n3. Complete implementation and tests.\n4. Commit focused changes and push.\n5. Create a concise PR with summary and test notes.\n\n## Guardrails\n\n- Keep branch scope focused on one change set.\n- Include verification notes before requesting review.\n\n## Output\n\n- New branch name\n- PR summary and test notes\n- PR URL",
"cost": {
"context_tokens": 139
}
}
Fetch it by URL: GET /api/v1/registry/velclaw-ocodejs-new-branch-and-pr/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.