commit-rules
commit-rules defines standardized commit message conventions and technical requirements used by other commit-related Claude Code skills in the Turbo repository. It specifies that commits must follow imperative mood with concise messages under 100 characters, excludes references to ignored files, and enforces direct git commit commands with mandatory GPG signing. Use this as a reference when implementing or understanding commit automation workflows.
git clone --depth 1 https://github.com/tobihagemann/turbo /tmp/commit-rules && cp -r /tmp/commit-rules/codex/skills/commit-rules ~/.claude/skills/commit-rulesSKILL.md
# 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, use `request_user_input` to let the user resolve it—they may need to approve a key prompt.
For each reviewer question on a PR, recall implementation reasoning and compose a raw answer. Use when the user asks to \"answer reviewer questions\", \"draft answers to PR questions\", or \"explain reviewer questions\".
Apply findings by making the suggested code changes. Applies accepted verdicts, escalates ambiguous findings to the user, and offers to note genuine improvements for later. Use when the user asks to \"apply findings\", \"apply fixes\", \"apply suggestions\", \"apply accepted findings\", \"fix the findings\", or \"apply the review results\".
Project-wide health audit pipeline that fans out to all analysis skills in parallel, evaluates findings, and produces a unified report at .turbo/audit.md. Use when the user asks to \"audit the project\", \"run a full audit\", \"project health check\", \"audit my code\", \"codebase audit\", or \"comprehensive review\".
Shared changelog conventions and formatting rules referenced by $create-changelog and $update-changelog. Not typically invoked directly.
Enforce mirror, reuse, and symmetry principles to keep new code consistent with surrounding code. Use when writing new code in an existing codebase, adding new features, refactoring, or making any code changes.
Run autonomous task execution using the codex CLI. Use when the user asks to \"codex exec\", \"run codex exec\", \"execute a task with codex\", or \"delegate to codex\".
Run AI-powered code review using the codex CLI. Use when the user asks to \"codex review\", \"run codex review\", or \"review a commit with codex\".
Commit already-staged changes and push in one step. Use when the user asks to \"commit and push staged changes\", \"commit and push what's staged\", or \"commit staged and push\".