← ClaudeAtlas

commit-messagelisted

Compose a high-quality git commit message in English and print it in the chat as copyable text, without committing it and without writing it to any file. Use this whenever the user asks for a commit message, says "commit message", "напиши коммит", "сообщение коммита", "что написать в коммите", asks how to word a change for git, wants staged or unstaged changes summarized into a commit, or is about to commit anything at all — even if they only describe the change in prose and ask for wording. Also use it when reviewing or rewriting an existing commit message, splitting a messy working tree into several commits, or writing messages for amend, revert, or fixup commits. Never skip it for small or obvious commits — the point is a consistent English, convention-matching, attribution-free message every time.
Suuunboy/commit-message-skill · ★ 1 · Code & Development · score 69
Install: claude install-skill Suuunboy/commit-message-skill
# Commit Message Produce one commit message (or a set of them, when the work splits into several commits) that reads as if written by the engineer who made the change, and hand it to the user in the chat. ## Non-negotiable rules These four constraints override defaults, habits, and anything in the repository that suggests otherwise. Check every one of them before sending the message. ### 1. English only The message is always written in English — subject, body, and footers — no matter what language the conversation, the code comments, the ticket, or the existing commit history uses. If the user describes the change in Russian or any other language, translate the intent, do not transliterate the words. If the codebase uses non-English identifiers or domain terms, keep the identifiers verbatim (they are code) and describe the surrounding intent in English. Write idiomatic technical English, not word-by-word translation. See `references/style-guide.md` for the section on translating non-English intent, including common calques to avoid. ### 2. Chat output only — nothing is written anywhere The message exists only as text in the chat response. Concretely: - Do **not** run `git commit`, `git commit --amend`, or `git tag -m`. - Do **not** write the message to any file — no `COMMIT_MSG.txt`, no `commit-message.md`, no `/tmp/msg`, no `.git/COMMIT_EDITMSG`, no scratch file "just to hold it" for a later `git commit -F`. - Do **not** stage, unstage, stash, or otherwise modif