git-commit-message skill
✓ VerifiedGenerates a structured commit message containing a summary line and a detailed body based on a provided staged diff.
- GitHub stars
- 497
- Files
- 1
- Last commit
- Nov 12, 2026
- License
- MIT
- Allowed tools
- —
What does the git-commit-message skill do?
git-commit-message generates a structured commit message containing a summary line and a detailed body based on a provided staged diff.
Summary generated from the skill's SKILL.md.
About the git-commit-message skill
Writing structured commit messages from staged code changes is the primary function of this tool. It assists developers who need to transform a technical diff into a clear summary line followed by a detailed body that explains the reasoning behind a change. An agent should load this skill when a user explicitly requests help with commit documentation or describes the task of writing a message based on code modifications.
The process begins by reading the provided input, which can be a file or specific text. The skill produces a formatted message that maintains the user's original wording where appropriate to ensure accuracy. To prevent errors, the tool will state plainly if the input is incomplete rather than attempting to guess the intent. After generating the message, it provides a brief list of what was changed or found so the user can verify the output before finalizing their git workflow.
What an agent can do with it
- 1Generate messages from staged diffsCreate a commit message that includes both a summary line and a body explaining the purpose of the changes.
- 2Verify commit content accuracyReview a list of changes made during the message generation process to ensure the description is correct.
- 3Handle incomplete code inputsIdentify when a provided diff is insufficient to write a meaningful message without making assumptions.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the git-commit-message skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the git-commit-message skill in Claude Code
~/.claude/skills/git-commit-message/SKILL.md
$ npx degit zhuyansen/agent-skills-hub/ops/skillmgr-runs/in/input/library/git-commit-message ~/.claude/skills/git-commit-messageInstall the git-commit-message skill in Claude Code (project)
.claude/skills/git-commit-message/SKILL.md
$ npx degit zhuyansen/agent-skills-hub/ops/skillmgr-runs/in/input/library/git-commit-message .claude/skills/git-commit-messageInstall the git-commit-message skill in Codex
~/.agents/skills/git-commit-message/SKILL.md
$ npx degit zhuyansen/agent-skills-hub/ops/skillmgr-runs/in/input/library/git-commit-message ~/.agents/skills/git-commit-messageInstall the git-commit-message skill in Gemini CLI
~/.gemini/skills/git-commit-message/SKILL.md
$ npx degit zhuyansen/agent-skills-hub/ops/skillmgr-runs/in/input/library/git-commit-message ~/.gemini/skills/git-commit-messageInstall the git-commit-message skill in Claude.ai
npx degit zhuyansen/agent-skills-hub/ops/skillmgr-runs/in/input/library/git-commit-message git-commit-message && zip -r git-commit-message.zip git-commit-message # claude.ai → Customize → Skills → + → Create skill → Upload a skill → git-commit-message.zip
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work · What to fix for more points
- Source repository linked and reachablezhuyansen/agent-skills-hub/ops/skillmgr-runs/in/input/library/git-commit-message is public and reachablegithub.com/zhuyansen/agent-skills-hub/tree/HEAD/ops/skillmgr ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-12github.com/zhuyansen/agent-skills-hub/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/zhuyansen/agent-skills-hub/blob/HEAD/ops/skillmgr ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/zhuyansen/agent-skills-hub/blob/HEAD/ops/skillmgr ↗Pass
- SKILL.md follows the Agent Skills formatthe description does not say when to use the skillgithub.com/zhuyansen/agent-skills-hub/blob/HEAD/ops/skillmgr ↗Finding
SKILL.md
View on GitHubGit Commit Message
Write a commit message from the staged diff: a short summary line and a body explaining why.
When to use
Use this skill when the user asks for it by name or describes this task. Do not use it for unrelated work.
Steps
- Read the input the user points to. If none is given, ask for the file or text.
- Do the task described above, step by step, and keep the user's own wording where it matters.
- Show the result, then a short list of what you changed or found, so the user can check it.
Notes
- Keep changes small and reversible.
- Say plainly when the input is incomplete instead of guessing.
Files in this skill
1git-commit-message skill questions
How do I install the git-commit-message skill in Claude Code?
Run npx degit zhuyansen/agent-skills-hub/ops/skillmgr-runs/in/input/library/git-commit-message ~/.claude/skills/git-commit-message. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the git-commit-message skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
What does this skill produce?
It generates a commit message consisting of a short summary line and a body that explains the reasoning behind the changes.
What should the agent do if the input is missing?
The agent should ask the user for the specific file or text instead of attempting to guess the content.