Compact commit msg
Use whenever writing a git commit message, including any `git commit` or `git commit -m` invocation. Triggers on creating a commit, committing changes, drafting a commit title or body, even when the commit is a subtask of a larger fix or feature. Apply BEFORE running `git commit`, not after.From its SKILL.md
npx -y skills add myl7/compact-commit-msg-skill --skill compact-commit-msgAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.3 KB, 226 tokens by cl100k_base, as published. Nobody here has run it
Template
[<type>: ]<title>
[<body>]
[<footers>, e.g.:]
[Fix #1, fix #2]
Read previous commit msgs to follow the existing preference. Default to no any optional parts.
Style
Commit msgs are for humans (developers) and have strict char limits. The more compact, the better. At most 72 chars for the title because GitHub truncates there. Use common abbrevations, e.g., dependency -> dep.
If the title is a single sentence, no period. Omit articles (a/an/the) if no confusion. Write proper nouns as-is.
Prefer no body. Only add it when something critical requires explanations. Note that developers rarely read the body. Consider proposing splitting the commit before adding a body.
Special Cases
When updating deps, use Update deps.
However, if the ecosystem distinguishes dev deps (e.g., Node, Poetry/uv, Cargo), use Update dev deps when only updating dev deps, so that users can confirm shipped/released deps are not updated.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 1 of the 12 instructions most pr commit review skills give in 226 tokens
Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-07
- Use conventional commits formatin 127 of 888, across 115 files
- Keep subject line under 72 charactershere, and in 62 of 888, across 48 files
- Delete branches after mergein 51 of 888, across 38 files
- Use imperative mood in subject linein 51 of 888, across 42 files
- Use imperative mood in commit messagesin 44 of 888
- Verify directory is ignored before creating worktreein 43 of 888, across 12 files
- Generate a conventional commit messagein 43 of 888
- Add unignored worktree directories to gitignorein 42 of 888, across 10 files
- Make atomic commitsin 39 of 888, across 27 files
- Run tests before committingin 36 of 888, across 25 files
- Verify clean test baselinein 35 of 888, across 9 files
- Split unrelated changes into separate commitsin 35 of 888, across 30 files
Said here and by no other author read
- apply this before running git commit
- follow the provided commit message template
- read previous commit messages to match existing preference
- omit all optional template parts by default
- use common abbreviations to shorten the message
- omit articles like a, an, or the
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.