# Git Commit > Guide for preparing git commits in this repository, including context gathering and repository-specific commit message conventions. Use when this capability is needed. - Skill: `tomevault-io/git-commit-18` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/git-commit-18` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/git-commit-18/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/git-commit-18 --- # Git Commit Workflow Use this skill when preparing or creating commits. ## Workflow 1. **Gather commit context in one tool call** - Run: `git status && git diff && git log -n 3 --format="---%n%B"`. 1. **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. 1. **Avoid Conventional Commit prefixes** - Do not use prefixes such as `feat:` or `fix:` in commit titles. 1. **Apply repository-specific commit rules** - Never use `--no-verify` with git commands to bypass `pre-commit` hooks. - Do not add `Co-Authored-By` trailers or AI attribution to commit messages. --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/opencloudtool) — claim your Tome and manage your conversions.