← ClaudeAtlas

git-commit-messagelisted

Use when writing a commit message or a merge or pull request's title or description, or deciding what type, scope or breaking-change marker a change takes — whether through a command or typed by hand, in a repository of any language. Owns the Conventional Commits 1.0.0 message shape, the rule that the type records which release the change earns and is chosen by what the change is rather than how large it was, why a commit that is not a release never touches the version, how a break is marked so a tool reading the history finds it, why a message says nothing about the tool or agent that wrote it, why it refers only to what outlives the work, and where the convention has to hold under a squash or a merge-commit strategy. Staging and committing is `/commit`; refusing a malformed message at commit time is `/install-commit-hook`; computing and cutting the release is `/release`. - Also when asked for a commit message, a conventional commit, whether a change is feat or fix, how to mark a breaking change, what a merg
wntic/pyhouse · ★ 3 · Code & Development · score 76
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