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.
If you’re asked to rename a file, directory, or any entity that maps to a file path, prefer a Git rename (git mv or equivalent) over delete+add.
Preserve history even when changing the file contents: rename first, then modify the moved file(s).
Avoid workflows that break rename detection (e.g., removing the old file and creating a new one with the same content).
After a file rename, ensure the code still matches project conventions (for example, C# class/file name alignment) without reverting the Git rename.
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 slot
curl -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 git-rename-history 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": "yarick-workshop-rotating-sonar-client-git-rename-history-rule",
"kind": "skill",
"name": "git-rename-history",
"description": "Preserve Git history when renaming files/classes",
"publisher": "Yarick-Workshop",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github-cursor-rules"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Preserve Git history when renaming files/classes"
],
"primary": false,
"metadata": {
"source": {
"provider": "github-cursor-rules",
"repository": "https://github.com/Yarick-Workshop/Rotating-Sonar-Client",
"path": ".cursor/rules/git-rename-history.mdc",
"ref": "cda2d3c461ed74c158cf6c473cf7dcd88ca8c1e4",
"url": "https://github.com/Yarick-Workshop/Rotating-Sonar-Client/blob/cda2d3c461ed74c158cf6c473cf7dcd88ca8c1e4/.cursor/rules/git-rename-history.mdc",
"key": "Yarick-Workshop/Rotating-Sonar-Client/.cursor/rules/git-rename-history.mdc"
}
},
"instructions": "# Rename guidance\n\n- If you’re asked to rename a file, directory, or any entity that maps to a file path, prefer a Git rename (`git mv` or equivalent) over delete+add.\n- Preserve history even when changing the file contents: rename first, then modify the moved file(s).\n- Avoid workflows that break rename detection (e.g., removing the old file and creating a new one with the same content).\n- After a file rename, ensure the code still matches project conventions (for example, C# class/file name alignment) without reverting the Git rename.",
"cost": {
"context_tokens": 135
}
}
Fetch it by URL: GET /api/v1/registry/yarick-workshop-rotating-sonar-client-git-rename-history-rule/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.
