← Back to Skills Marketplace
Commit Message Validation
by
omaression
· GitHub ↗
· v1.0.0-alpha
· MIT-0
183
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install commit-message-writing
Description
Strict Conventional Commits v1.0.0, atomic commit discipline, and Trunk-Based Development guardrails for git work. Use when preparing a commit, staging chang...
README (SKILL.md)
Commit Message Writing
Every commit: valid Conventional Commit, atomic, on the right short-lived branch.
Required workflow
git status --shortandgit diff --stat.- Verify you're on a short-lived branch dedicated to one feature, bug, fix, or coding area. If not, create/switch first.
- Confirm the changes are one logical unit. If mixed, split before committing.
- Confirm automated tests appropriate to the scope will run.
- Pick the most specific commit type.
- Write the message:
\x3Ctype>[optional scope][!]: \x3Cimperative lowercase description>
[optional body]
[optional footer(s)]
- Validate with
scripts/validate_commit_message.pybefore committing.
Hard rules
- One short-lived branch per feature, bug, fix, or distinct coding area.
- Keep branches narrow, merge back quickly, avoid long-lived divergence.
- Every PR must have robust automated tests so bugs are caught early.
- Always include a lowercase type followed by
:. - Imperative, lowercase description, no trailing period, ≤72 chars.
- Body: one blank line after description. Footers: one blank line after body.
- Footer format:
Token: value. Hyphens in tokens exceptBREAKING CHANGE. - Use
!and/orBREAKING CHANGE:footer for breaking changes. - Never use
WIP,misc,update, or vague summaries.
Types
| Type | When | SemVer |
|---|---|---|
feat |
new feature | minor |
fix |
bug fix | patch |
refactor |
restructure, no behavior change | none |
perf |
performance improvement | none (patch if fixes bug) |
docs |
documentation only | none |
test |
tests only | none |
build |
build system / deps | none |
ci |
CI/CD changes | none |
chore |
maintenance / tooling | none |
style |
formatting only | none |
revert |
revert prior commit | depends |
Scope
Use a consistent noun for the dominant area. Omit only when truly cross-cutting. Never multiple scopes in one commit line.
Splitting rules
Split when:
- feature + bug fix
- code + formatting-only cleanup
- deps/build + application logic
- refactor + standalone behavior change
- generated files + loosely coupled source
One type, one intent per commit. If you can't describe it that way, split.
Validation
python3 scripts/validate_commit_message.py --message "feat(auth): add otp fallback"
Usage Guidance
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.
Capability Analysis
Type: OpenClaw Skill
Name: commit-message-writing
Version: 1.0.0-alpha
The skill bundle is a legitimate utility for enforcing Conventional Commits v1.0.0 standards. It contains a Python validation script (validate_commit_message.py), a supporting shell script for git hooks (commit-msg-hook.sh), and clear instructions in SKILL.md. The code uses standard libraries (argparse, re) for string validation and contains no evidence of data exfiltration, malicious execution, or prompt injection attempts.
Capability Assessment
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.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install commit-message-writing - After installation, invoke the skill by name or use
/commit-message-writing - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0-alpha
- Initial release of commit-message-writing skill (v1.0.0-alpha).
- Enforces strict Conventional Commits v1.0.0 and atomic commit discipline.
- Includes step-by-step workflow with validation requirements before committing.
- Details hard rules for branch strategy, commit formatting, scope usage, and splitting commits.
- Provides clear type definitions and rules for composing commit messages and footers.
- Adds guidance for PR test requirements and commit message validation script usage.
Metadata
Frequently Asked Questions
What is Commit Message Validation?
Strict Conventional Commits v1.0.0, atomic commit discipline, and Trunk-Based Development guardrails for git work. Use when preparing a commit, staging chang... It is an AI Agent Skill for Claude Code / OpenClaw, with 183 downloads so far.
How do I install Commit Message Validation?
Run "/install commit-message-writing" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Commit Message Validation free?
Yes, Commit Message Validation is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Commit Message Validation support?
Commit Message Validation is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Commit Message Validation?
It is built and maintained by omaression (@omaression); the current version is v1.0.0-alpha.
More Skills