git-branchinglisted
Install: claude install-skill wntic/pyhouse
# Git — Branching
How a change travels from a branch to the mainline, and what the history looks like when it arrives.
This skill assumes no language, forge or team size, and it names no strategy as the right one: it
states what holds under every strategy, binds the lightest one below, and says what a heavier one
has to earn.
**Precondition — who runs a version other than the latest.** Most rules hold for any repository.
One depends on the answer:
| Does anything… | If no, this does not apply |
|---|---|
| run, or depend on, a released version other than the latest | rule 8 — nothing needs a fix on an old line, so every fix ships as the next number |
## When to use vs. neighbours
- What a commit's message says, its type, and where the convention has to hold under each merge
method → `git-commit-message`. This skill picks the merge method; that one says what the choice
obliges each message to be.
- Working out the next version from the history and cutting the release commit and tag → `/release`.
- What a version number promises, and the tag's own form → the ecosystem's versioning rules; for a
Python distribution, for example, `python-versioning`, in the `pyhouse-universal` plugin.
- Refusing a malformed message at commit time → `/install-commit-hook`. It checks a message's shape,
not which branch it lands on.
## Template — short-lived branches off one mainline, every commit kept
What the repository records, where contributors read — a `CONTRIBUTING` file, an age