| name | git-commit |
| description | Guide for preparing git commits in this repository, including context gathering and repository-specific commit message conventions. |
Git Commit Workflow
Use this skill when preparing or creating commits.
Workflow
-
Gather commit context in one tool call
- Run:
git status && git diff && git log -n 3 --format="---%n%B".
-
Write commit title and description
- Use a concise summary on the first line (the title) in present simple tense
(example:
Fix cursor offset).
- Leave one blank line between the title and the body.
- Add a body only when it improves clarity.
- Explain why and how in present simple tense.
- If there are multiple points, format them as
- bullet lines with one point per
line.
-
Avoid Conventional Commit prefixes
- Do not use prefixes such as
feat: or fix: in commit titles.
-
Apply repository-specific commit rules
- Never use
--no-verify with git commands to bypass prek-managed hooks.
- Do not add
Co-Authored-By trailers or AI attribution to commit messages.