ClawHub

Commit Message Validation

v1.0.0-alpha

Strict Conventional Commits v1.0.0, atomic commit discipline, and Trunk-Based Development guardrails for git work. Use when preparing a commit, staging chang...

⭐ 0· 143·0 current·0 all-time
by@omaression
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 name/description advertise Conventional Commits enforcement and trunk-based guardrails; the repository includes a validator script, a commit-msg hook that runs the validator, and tests — all consistent with that purpose.
✓
Instruction Scope
SKILL.md instructs the agent to run simple git checks and to validate messages with scripts/validate_commit_message.py. The validator only reads the supplied commit message (argument, file, or stdin) and doesn't access other system files, environment variables, or external endpoints.
✓
Install Mechanism
There is no automated install spec (instruction-only). Hook installation is manual (copy into .git/hooks). No downloads, package installs, or remote code fetches are present.
✓
Credentials
The skill requires no environment variables, credentials, or config paths. The code does not reference secrets or unrelated environment state.
✓
Persistence & Privilege
always is false and the skill does not request persistent system privileges. Installing the commit hook is an explicit manual action by the user and the hook only runs the local validator script if present.
Assessment
This skill appears to do exactly what it says: validate commit messages locally. There are no network calls or credential requests. If you plan to use it, manually copy scripts/commit-msg-hook.sh into .git/hooks/commit-msg and ensure the validator path resolution matches your repo layout (the hook searches a few relative paths for scripts/validate_commit_message.py). Note the hook will skip validation if it can't find the validator (prints a warning) and the validator will block commits by returning non-zero on invalid messages. You may want to run the bundled tests (tests/test_validate_commit_message.py) or inspect validate_commit_message.py to confirm the exact rules match your team's policy before enabling the hook.

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

latestvk976vrmreg3qr2mpccaxskjke5831k6y

License

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

Comments