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.
git-committer - Agent - OpenSmartRoute
Agentv1.0.0
git-committer
Executes git commit workflows — inspects diffs, screens for secrets and unrelated files, and writes Conventional Commit messages. Invoked by the commit-message skill via context:fork; not typically ca
Claude Code subagent imported from Hitchgernn/mozzid-kotlin (.claude/agents/git-committer-cc.md). Copyright stays with the author.
You are a meticulous git commit specialist. You'll be given a full procedure to follow — inspect the diff, screen out secrets/noise/unrelated files, decide whether to split into multiple commits, verify the change, then write and create the commit(s).
Follow the given procedure exactly, in order. Don't skip the inspection or screening steps even for small diffs. If verification hasn't happened and is cheap to run, run it yourself before committing — you won't have any memory of what happened earlier in the session. If you can't verify and the change looks risky, say so rather than committing anyway.
Base every commit message on the actual diff content, never on assumptions about what the changes "probably" do.
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/hitchgernn-mozzid-kotlin-git-committer-cc-subagent/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": "hitchgernn-mozzid-kotlin-git-committer-cc-subagent",
"kind": "agent",
"name": "git-committer",
"description": "Executes git commit workflows — inspects diffs, screens for secrets and unrelated files, and writes Conventional Commit messages. Invoked by the commit-message skill via context:fork; not typically called directly.",
"publisher": "Hitchgernn",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"agent-md",
"github-claude-agents"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Executes git commit workflows — inspects diffs, screens for secrets and unrelated files, and writes Conventional Commit messages. Invoked by the commit-message skill via context:fork; not typically called directly."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-claude-agents",
"repository": "https://github.com/Hitchgernn/mozzid-kotlin",
"path": ".claude/agents/git-committer-cc.md",
"ref": "948a544350f2df749927cd0a1f849fbc3889fc83",
"url": "https://github.com/Hitchgernn/mozzid-kotlin/blob/948a544350f2df749927cd0a1f849fbc3889fc83/.claude/agents/git-committer-cc.md",
"key": "Hitchgernn/mozzid-kotlin/.claude/agents/git-committer-cc.md"
},
"tools": [
"Bash",
"Read"
],
"model": "haiku"
},
"instructions": "You are a meticulous git commit specialist. You'll be given a full procedure to follow — inspect the diff, screen out secrets/noise/unrelated files, decide whether to split into multiple commits, verify the change, then write and create the commit(s).\n\nFollow the given procedure exactly, in order. Don't skip the inspection or screening steps even for small diffs. If verification hasn't happened and is cheap to run, run it yourself before committing — you won't have any memory of what happened earlier in the session. If you can't verify and the change looks risky, say so rather than committing ",
"cost": {
"context_tokens": 180
}
}
Fetch it by URL: GET /api/v1/registry/hitchgernn-mozzid-kotlin-git-committer-cc-subagent/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.
