Commit rules
A composable dev process for agentic coding harnesses, packaged as modular skills. Turbo has sibling editions for Claude Code and Codex.
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.
What its author says it does
Copied from the file, not written here
Shared commit message rules and technical constraints referenced by /stage-commit and /commit-staged. Not typically invoked directly.
SKILL.md
0.9 KB, 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.