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.
Commit And Diary Rule - Skill - OpenSmartRoute
Skillv1.0.0
Commit And Diary Rule
Use when making code or configuration changes in this project. Enforces post-change git commit with a clear message and update of project diary markdown with the same clear summary.
Instruction file imported from SysQuirrel/RAG-CLI (.github/instructions/commit-and-diary.instructions.md). Copyright stays with the author.
Commit And Diary Rule
After completing implementation work, always run a git commit.
Commit messages must be clear, specific, and describe what was changed.
Use the imperative style in commit messages when possible.
Do not use vague commit messages like "update" or "fix stuff".
For every commit, update the project diary markdown file at FEATURES_AND_PIPELINE.md.
Add a concise change note that mirrors the commit intent.
Include date, problem, what changed, and outcome in the diary entry.
Keep diary wording consistent with the commit message so history stays traceable.
If there are no source changes to commit, explicitly state that no commit was needed.
If commit cannot be made (for example user blocked it), explain the blocker and suggest the exact commit command.
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}'
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": "sysquirrel-rag-cli-commit-and-diary-instructions",
"kind": "skill",
"name": "Commit And Diary Rule",
"description": "Use when making code or configuration changes in this project. Enforces post-change git commit with a clear message and update of project diary markdown with the same clear summary.",
"publisher": "SysQuirrel",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github-instructions"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Use when making code or configuration changes in this project. Enforces post-change git commit with a clear message and update of project diary markdown with the same clear summary."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-instructions",
"repository": "https://github.com/SysQuirrel/RAG-CLI",
"path": ".github/instructions/commit-and-diary.instructions.md",
"ref": "01972bc3c138bf5ce973cecce6b1d51e2ad1e32f",
"url": "https://github.com/SysQuirrel/RAG-CLI/blob/01972bc3c138bf5ce973cecce6b1d51e2ad1e32f/.github/instructions/commit-and-diary.instructions.md",
"key": "SysQuirrel/RAG-CLI/.github/instructions/commit-and-diary.instructions.md"
},
"applies_to": "**"
},
"instructions": "# Commit And Diary Rule\n\n- After completing implementation work, always run a git commit.\n- Commit messages must be clear, specific, and describe what was changed.\n- Use the imperative style in commit messages when possible.\n- Do not use vague commit messages like \"update\" or \"fix stuff\".\n\n- For every commit, update the project diary markdown file at `FEATURES_AND_PIPELINE.md`.\n- Add a concise change note that mirrors the commit intent.\n- Include date, problem, what changed, and outcome in the diary entry.\n- Keep diary wording consistent with the commit message so history stays traceable.\n\n- I",
"cost": {
"context_tokens": 200
}
}
Fetch it by URL: GET /api/v1/registry/sysquirrel-rag-cli-commit-and-diary-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.
