Commit Message
Draft an accurate commit message from a specified or staged change set using the repository's established style. Use when asked for commit wording, including conventional commits only when requested or evidenced by project history.
Install
$ agentstack add skill-avacadorun-dev-soba-agent-commit-message ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Commit Message
Purpose
Describe one commit's actual intent and impact in the style expected by its repository.
Triggers
Apply this workflow when the user asks for commit wording based on staged changes, a supplied patch, or an explicit commit range.
Inputs To Inspect
- Project instructions, commit template, and contribution guidance.
- The exact change set the message should describe.
- Recent repository commit style when explicit rules are absent.
- Tests, migrations, or compatibility changes visible in the change set.
Procedure
- Resolve the exact change boundary and confirm it contains meaningful changes.
- Identify the dominant user or maintainer outcome rather than listing files.
- Match the repository's established subject format, language, capitalization, scope, and length.
- Use Conventional Commits only when the user requests it or repository evidence establishes it.
- Write a concise imperative subject where that matches project style; otherwise follow the local convention.
- Add a body only to explain motivation, non-obvious behavior, risk, migration, or multiple tightly related parts.
- Add references, acknowledgements, or breaking-change markers only when supported by the request or change evidence.
- Offer multiple options only when the change genuinely supports different emphasis.
Verification Contract
Ensure every claim is visible in the resolved change set and the message follows the discovered repository convention. Exclude unstaged, unrelated, or merely planned work unless the user explicitly selected it.
Failure Recovery
If no change set can be resolved, state what is missing instead of inventing a message. If the change mixes unrelated outcomes, flag that a split may produce clearer history and provide messages per coherent unit when useful.
Memory Policy
Do not write memory. Treat current project instructions and repository history as the source of commit conventions.
Stop Conditions
Stop after providing message text ready to use, or after identifying the missing change boundary needed for an accurate message.
Anti-Patterns
- Do not force Conventional Commits onto a repository that does not use them.
- Do not invent issue identifiers, motivations, test results, or breaking changes.
- Do not reduce a behavioral change to a vague file-operation subject.
- Do not create a commit unless the user explicitly asks for that separate action.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: avacadorun-dev
- Source: avacadorun-dev/soba-agent
- License: MIT
- Homepage: https://soba-agent.dev/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.