Commit Rules

SkillCommunication

Shared commit message rules and technical constraints referenced by $stage-commit and $commit-staged. Not typically invoked directly.

Available today. Use it from your connected AI after setup.

No other account needed.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Commit Rules skill

What this skill tells your AI

The instructions your AI receives, as published by tobihagemann/turbo in codex/skills/commit-rules/SKILL.md and read by ahel’s review.

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.

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.

Advanced