ClawHub

Conventional Commits

v1.0.1

Format commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.

⭐ 4· 7.9k·57 current·62 all-time
byTiago Bastos@bastos
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The skill's name and description match the SKILL.md content: both describe formatting commit messages according to the Conventional Commits spec. There are no extra binaries, env vars, or unrelated requirements.
✓
Instruction Scope
SKILL.md contains only guidance and examples for composing commit messages. It does not instruct the agent to read files, access environment variables, call external endpoints, or execute system commands beyond generating text for commit messages.
✓
Install Mechanism
No install specification or code files are present. This is the lowest-risk model (instruction-only) and nothing will be written to disk or downloaded during install.
✓
Credentials
The skill declares no environment variables, credentials, or config paths. Nothing requested appears disproportionate to the described purpose of generating/formating commit messages.
✓
Persistence & Privilege
The skill is not marked always:true and uses the default model-invocation settings. It does not request persistent system privileges or attempt to modify other skills or system-wide settings.
Assessment
This skill is instruction-only and simply provides rules and examples for writing Conventional Commits — it does not install software or request credentials. Before relying on it: (1) review any commit messages the agent generates before you actually run git commit, since messages can trigger CI/release automation; (2) if your repository has additional or stricter commit conventions, verify compatibility; and (3) avoid granting broader privileges (for example always:true or automated commit execution) unless you explicitly want the agent to operate on your repo without manual confirmation.

Like a lobster shell, security has layers — review code before you run it.

latestvk975768dz7j8t23gyckk4dr2td804vce

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments