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.
In-Branch API Compatibility - Skill - OpenSmartRoute
Skillv1.0.0
In-Branch API Compatibility
Use when refactoring or evolving in-progress APIs within the same branch, or deciding whether to add compatibility wrappers, adapter layers, or deprecated aliases for interface changes under developme
Instruction file imported from TsumiNa/dango (.github/instructions/in-branch-api-compat.instructions.md). Copyright stays with the author.
In-Branch API Compatibility
For APIs that are only in progress on the current branch, add wrappers, adapter layers, deprecated aliases, or parallel interfaces only when the user asks in the current request to preserve compatibility, such as by keeping an old name, adapter, or alias.
Prefer updating call sites directly and keeping one current interface.
If compatibility may matter for released code, cross-branch coordination, or external consumers, prioritize that concern over the in-branch cleanup rule and state the assumption before adding compatibility code.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
yaml
targets:
- https://api.opensmartroute.ai/api/v1/registry/tsumina-dango-in-branch-api-compat-instructions/manifest # or paste the manifest below
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
{
"ocm": "1",
"id": "tsumina-dango-in-branch-api-compat-instructions",
"kind": "skill",
"name": "In-Branch API Compatibility",
"description": "Use when refactoring or evolving in-progress APIs within the same branch, or deciding whether to add compatibility wrappers, adapter layers, or deprecated aliases for interface changes under development.",
"publisher": "TsumiNa",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github-instructions"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Use when refactoring or evolving in-progress APIs within the same branch, or deciding whether to add compatibility wrappers, adapter layers, or deprecated aliases for interface changes under development."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-instructions",
"repository": "https://github.com/TsumiNa/dango",
"path": ".github/instructions/in-branch-api-compat.instructions.md",
"ref": "b646e24a9ee69d3ac309675a8be8bd8e71136d77",
"url": "https://github.com/TsumiNa/dango/blob/b646e24a9ee69d3ac309675a8be8bd8e71136d77/.github/instructions/in-branch-api-compat.instructions.md",
"key": "TsumiNa/dango/.github/instructions/in-branch-api-compat.instructions.md"
}
},
"instructions": "# In-Branch API Compatibility\n\n- For APIs that are only in progress on the current branch, add wrappers, adapter layers, deprecated aliases, or parallel interfaces only when the user asks in the current request to preserve compatibility, such as by keeping an old name, adapter, or alias.\n- Prefer updating call sites directly and keeping one current interface.\n- If compatibility may matter for released code, cross-branch coordination, or external consumers, prioritize that concern over the in-branch cleanup rule and state the assumption before adding compatibility code.",
"cost": {
"context_tokens": 143
}
}
Fetch it by URL: GET /api/v1/registry/tsumina-dango-in-branch-api-compat-instructions/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.
