$npx -y skills add tobihagemann/turbo --skill commit-rulesShared commit message rules and technical constraints referenced by /stage-commit and /commit-staged. Not typically invoked directly.
| 1 | # Commit Rules |
| 2 | |
| 3 | ## Commit Message Rules |
| 4 | |
| 5 | - Match the style from `git log -n 10 --oneline` |
| 6 | - Concise and descriptive |
| 7 | - Imperative mood, present tense |
| 8 | - Aim for ≤100 characters in the subject |
| 9 | - No commit description—summarize everything in the message |
| 10 | - 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. |
| 11 | |
| 12 | ## Technical Constraints |
| 13 | |
| 14 | - Use `git commit -m "message"` directly—do not use heredoc syntax (sandbox blocks temp file creation) |
| 15 | - 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. |