# Commit Rules

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

- Skill: `majiayu000/commit-rules-4` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/commit-rules-4`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/commit-rules-4/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/commit-rules-4

---


# 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.