← 返回 Skills 市场

Commit Message Validation

Name: Commit Message Validation
Author: omaression

作者 omaression · GitHub ↗ · v1.0.0-alpha · MIT-0

cross-platform ✓ 安全检测通过

183

总下载

当前安装

版本数

在 OpenClaw 中安装

/install commit-message-writing

功能描述

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

使用说明 (SKILL.md)

Commit Message Writing

Every commit: valid Conventional Commit, atomic, on the right short-lived branch.

Required workflow

git status --short and git 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.py before 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 except BREAKING CHANGE.
Use ! and/or BREAKING 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"

安全使用建议

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.

功能分析

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.

能力评估

✓ 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.

如何使用

确保已安装 OpenClaw（本地或 Docker 部署）
在对话框中输入安装命令：/install commit-message-writing
安装完成后，直接呼叫该 Skill 的名称或使用 /commit-message-writing 触发
根据 Skill 的参数说明提供必要输入，即可获得结构化输出

版本历史

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.

元数据

Slug commit-message-writing

版本 1.0.0-alpha

许可证 MIT-0

累计安装 0

当前安装数 0

历史版本数 1

常见问题