commit-messagelisted
Install: claude install-skill xobotyi/cc-foundry
# Commit Message Format
<scope>
These rules apply only to git commit messages. Do not apply the line-length limits, the format
rules, or the structure rules of this skill to other files. Code, documentation, and configuration
files keep their own rules.
</scope>
A commit message is a factual record of one change. It tells the reader why the change happened. The reader has the diff
and the docs. The message adds only what the diff and the docs cannot show.
## What Makes a Good Message
<context-principle>
Draw the _why_ from three sources: the task that you solved, the reason that this approach won, and
the code that you built. Do not copy the sources into the message. If the context is incomplete,
record what the code and the available information can verify.
</context-principle>
## Structure
<format>
The message has three blocks. A blank line separates the blocks:
```text
[scope] subject
body
trailers
```
- **Subject** — what changed.
- **Body** — the reason for the change, and the procedure that verifies it.
- **Trailers** — structured metadata such as references and authorship.
</format>
### ASCII Symbols
<charset>
Use ASCII punctuation and ASCII symbols only. Prose in a different language is correct. This rule
applies to decorative and typographic Unicode, not to natural language.
- No em dash and no en dash (—, –). Use `--` or `-`.
- No arrows (→, ←, ↔). Use `->`, `<-`, and `<->`.
- No bullet symbols (•, ▸). Use `-` or `*`.
- No fancy quotes (“”, ‘’). Use st