Commit rules
Shared commit message rules and technical constraints referenced by /stage-commit and /commit-staged. Not typically invoked directly.From its SKILL.md
npx -y skills add tobihagemann/turbo --skill commit-rulesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- runs commandsInstructs the agent to run 2 commands, including `git commit -m "message"` and 1 more.
SKILL.md
0.9 KB, 186 tokens by cl100k_base, as published. Nobody here has run it
Commit Rules
Commit Message Rules
- 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.
Technical Constraints
- 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, useAskUserQuestionto let the user resolve it—they may need to approve a key prompt.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.