Commit Rules

tobihagemann/commit-rules

Shared commit message rules and technical constraints referenced by /stage-commit and /commit-staged. Not typically invoked directly.

240 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

398

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/tobihagemann/turbo --skill commit-rules

3 sections, as written by the author

Match the style from git log -n 10 --oneline
Concise and descriptive
Imperative mood, present tense
Aim for ≤100 characters in the subject
No commit description—summarize everything in the message
Don't reference .turbo/ content (filenames, requirement IDs, shell references, headings) in commit messages. .turbo/ is gitignored, so these references would be opaque to anyone reading without local copies.

Use git commit -m "message" directly—do not use heredoc syntax (sandbox blocks temp file creation)
Never bypass commit signing (--no-gpg-sign, -c commit.gpgsign=false). If signing fails, use AskUserQuestion to let the user resolve it—they may need to approve a key prompt.

Copy the folder

Take tobihagemann/commit-rules from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.