Generate a concise conventional-commit subject, optional body, and alternatives from a staged Git diff summary.
Install & Download
1. ClawHub CLI
The fastest way to install a skill directly from the registry.
npx clawhub@latest install git-commit-message-helper
2. Manual Installation
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
3. Prompt Installation
Copy this prompt to OpenClaw to install it automatically.
Help me install git-commit-message-helper using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Prefer to download?
Get the raw skill files in a ZIP archive.
What is Git Commit Message Helper?
Git Commit Message Helper is an Openclaw Skills workflow that turns a staged change summary into clear, consistent conventional-commit messages. It identifies an appropriate commit type, such as feat, fix, docs, refactor, test, or chore, and produces an imperative subject of 72 characters or fewer.
The skill is designed for developers who want fast commit-message guidance without granting commit or push access. It can work from a user-provided diff or stat and may optionally run a read-only Git command when the user approves it.
Git Commit Message Helper Use Cases
- Write a commit message after staging changes with
git add. - Convert a staged diff summary into a conventional-commit subject.
- Select an appropriate commit type for a feature, fix, documentation update, refactor, test, or maintenance change.
- Receive one recommended message plus two concise alternatives.
- Standardize commit wording while preserving a read-only, no-network workflow.
- Ask for the required diff or stat when no change summary is available.
How Git Commit Message Helper Works
- Detect whether the user is requesting a commit message, typically after staging changes.
- Check for a user-provided diff or summary. If none is available, request that the user paste one or run a cached-diff stat command.
- Review the change context and choose one conventional-commit type:
feat,fix,docs,refactor,test, orchore. - Compose a primary subject in imperative mood, limited to 72 characters and without a trailing period.
- Optionally add a concise body when additional context is useful.
- Provide two short alternative messages alongside the primary recommendation.
- Stop after generating suggestions; the skill does not commit, push, access the network, or modify repository state.
Git Commit Message Helper Setup
No separate package installation or configuration command is specified by the skill. Make the Git Commit Message Helper available in your Openclaw Skills environment, then stage the relevant changes if needed.
When a summary is not already available, the user may approve this read-only command:
git diff --cached --stat
The only declared executable dependency is git, and it is optional when the user supplies the diff or stat directly. The skill does not require network access and does not perform commits or pushes.
Git Commit Message Helper Data Schema & Taxonomy
The skill uses a compact input-and-output structure rather than generating repository files.
| Element | Format or rule |
|---|---|
| Input | User-provided staged diff summary, diff, or cached Git stat |
| Optional command | git diff --cached --stat |
| Commit type | feat, fix, docs, refactor, test, or chore |
| Subject | Imperative mood, maximum 72 characters, no trailing period |
| Scope | Optional conventional-commit scope inferred from the change, such as auth |
| Body | Optional explanatory text when useful |
| Recommendations | One primary message and two short alternatives |
| Generated files | None; the skill only returns message suggestions |
| Repository changes | None; it does not commit, push, or modify files |
Example taxonomy: fix(auth): handle empty password field uses fix as the type, auth as the scope, and an imperative subject describing the change.
Git Commit Message Helper Advanced Features
- Conventional-commit type selection across feature, bug-fix, documentation, refactoring, testing, and maintenance changes.
- Optional scope inference from the staged change context.
- Three-option output: one primary recommendation and two alternatives.
- Optional commit body for additional implementation context.
- Read-only Git inspection through an approved cached-stat command.
- No-network operation with no commit, push, or file-modification capability.
- Permission-aware behavior that requests the diff or stat when the required context is missing.
SKILL.md
Loading
Related Openclaw Skills
RFC Summarizer
Turn IETF RFC text into a concise engineering briefing that explains the problem, mechanism, security considerations, and caveats.
Browser Automation Agent
Browser Automation Agent controls a headed Chromium browser to interact with authorized websites, including pages that require a login.
Git Repository Health Auditor
Review a selected Git repository for maintainability, configuration, dependency, secret-exposure, and CI/CD risks without modifying files by default.
Regex Explainer
Turn an unfamiliar regular expression into a clear, token-by-token explanation with examples and likely bug warnings.
Pro Summarizer
A paid AI summarization skill that produces concise summaries, SEO keywords, and deeper insights in a strict JSON format.
Kubernetes Rollout Doctor
Kubernetes Rollout Doctor reviews pasted Makefile content for safer, more discoverable targets and can use kubectl for cluster checks when requested.
Featured*
