git-commit-messagelisted
Install: claude install-skill wntic/pyhouse
# Git — Commit Message
A commit message is the one record of a change that every later reader has: the reviewer, the person
running `git log` a year on, and the tool that works out the next release. This skill is what that
message has to say and where it says it. It assumes no language, package manager or forge, and it
states no staging or committing procedure — that is `/commit`'s.
The obligation underneath survives any convention: **a message records what kind of change it is, in a
position a tool can read, because that kind decides the release.** Conventional Commits 1.0.0 is the
binding below; every rule above it holds under another.
## When to use vs. neighbours
- Staging files, reading the diff and committing in one step → `/commit`.
- Refusing a malformed message at commit time instead of trusting everyone to remember →
`/install-commit-hook`, which installs a `commit-msg` hook that checks the parts of this skill a
machine can check: the shape, the blank line before a body, the uppercase break token and the subject
length.
- Which merge method a repository uses, how a branch's history is cleaned before it lands, and what
may never be rewritten → `git-branching`. Rule 9 below is what that choice obliges each message to be.
- Working out the next version from the types since the last tag, and cutting the one release commit
that rule 2 lets touch it → `/release`, which proposes and cuts only on an explicit yes.
- What a version number promises, and what coun