Claude
Skill
commit-rules
Shared commit message rules and technical constraints referenced by $stage-commit and $commit-staged. Not typically invoked directly.
Virus-scanned
Reviewed automatically before listing.
Download
tobihagemann-turbo-codex_skills_commit-rules-b903a85.zip · 0 KB
Install
skills CLI
npx skills add https://github.com/tobihagemann/turbo/tree/main/codex/skills/commit-rules
Claude Code
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install tobihagemann-turbo@llmmart
Git
git clone https://github.com/tobihagemann/turbo.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole tobihagemann/turbo collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
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, acceptance criteria, step numbers, 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, userequest_user_inputto let the user resolve it—they may need to approve a key prompt.
Files (turbo)
-
SKILL.md 964 B
--- name: commit-rules description: "Shared commit message rules and technical constraints referenced by $stage-commit and $commit-staged. Not typically invoked directly." --- # 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, acceptance criteria, step numbers, 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, use `request_user_input` to let the user resolve it—they may need to approve a key prompt.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.