Commit Rules

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

majiayu000 e51059e 2 files · 1.7 KB Updated 567 repo stars

File contents

Commit Rules

Commit Message Rules

  • Match the style from git log -n 10 --oneline
  • Concise and descriptive
  • Imperative mood, present tense
  • No commit description—summarize everything in the message
  • Don't reference .turbo/ content (filenames, IDs, 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.

majiayu000/claude-skill-registry-data/tree/main/development/unknown-tobihagemann-turbo-19 commit e51059e26e

Frequently asked questions

npx skillmds add majiayu000/commit-rules-4