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.
Use ISO 8601 date format (YYYY-MM-DD) for release entries
Write changelog entries from the user's perspective, not the developer's
Group changes by type, not by PR or commit
Link version headers to comparison URLs on the repository host
In CONTRIBUTING.md, document the commit message format the project expects
Explain the branching strategy and PR workflow
Include setup instructions for the development environment
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/willvelida-support-agent-hack-commit-messages-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": "willvelida-support-agent-hack-commit-messages-instructions",
"kind": "skill",
"name": "commit-messages",
"description": "Commit message and changelog conventions",
"publisher": "willvelida",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"github-instructions"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Commit message and changelog conventions"
],
"primary": false,
"metadata": {
"source": {
"provider": "github-instructions",
"repository": "https://github.com/willvelida/support-agent-hack",
"path": ".github/instructions/commit-messages.instructions.md",
"ref": "f46b0bce44b9a43d12e832ba61cdfd18aab566d0",
"url": "https://github.com/willvelida/support-agent-hack/blob/f46b0bce44b9a43d12e832ba61cdfd18aab566d0/.github/instructions/commit-messages.instructions.md",
"key": "willvelida/support-agent-hack/.github/instructions/commit-messages.instructions.md"
},
"applies_to": "**/CHANGELOG.md,**/CONTRIBUTING.md"
},
"instructions": "# Commit and Changelog Conventions\n\nWhen creating or editing changelog and contributing files:\n\n- Follow Keep a Changelog format: Unreleased, Added, Changed, Deprecated, Removed, Fixed, Security\n- Use ISO 8601 date format (YYYY-MM-DD) for release entries\n- Write changelog entries from the user's perspective, not the developer's\n- Group changes by type, not by PR or commit\n- Link version headers to comparison URLs on the repository host\n- In CONTRIBUTING.md, document the commit message format the project expects\n- Explain the branching strategy and PR workflow\n- Include setup instructions for t",
"cost": {
"context_tokens": 156
}
}
Fetch it by URL: GET /api/v1/registry/willvelida-support-agent-hack-commit-messages-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.
