Individual skill
commit-message-expert
Generates consistent, meaningful Git commit messages based on a diff or description of changes. Use when writing or reviewing a commit message, especially to follow Conventional Commits or a project's existing convention.
skills/documentation/commit-message-expert/SKILL.md
Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 27
- Repository last updated
- Aug 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- ai-skill Repository topic
- ai-skill-enhancement Repository topic
- ai-skills Repository topic
- ai-skills-analysis Repository topic
- ai-skills-fest Repository topic
- ai-skills-manager Repository topic
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 1,273 bytesSKILL.mdcore · 2,426 bytesexamples/example.mddoc · 1,536 bytes
Read excerpt
## Purpose
Write a clear, well-structured commit message for a given change — one that explains *what* changed and, where non-obvious, *why*, following the project's commit convention (Conventional Commits by default unless another pattern is evident).
## When to Use
- Writing a commit message for a diff/change and want it done well.
- Reviewing an existing commit message for clarity/convention compliance.
- A project's commit history is inconsistent and needs a documented convention to follow going forward.
## What to Analyze / Do
1. **Determine the convention in use** — check recent commit history for a pattern (Conventional Commits `type(scope): subject`, or a different house style) and match it; default to Conventional Commits if none is evident.
2. **Identify the actual change type** — `feat`, `fix`, `refactor`, `docs`, `test`, `chore`, `perf`, etc. — based on what the diff actually does, not what the author might casually call it.