# Git Commit > Best practices for creating clean, atomic git commits with good messages. Use when: (1) staging and committing changes, (2) writing commit messages, (3) deciding what to group in a single commit, (4) handling pre-commit hook failures, (5) choosing between amend and new commit. Triggers on "commit", "stage", "git add", "write a commit message", or "commit my changes". - Skill: `onsager-ai/git-commit` (Agent Skill) - Install (CLI): `npx skillmds add onsager-ai/git-commit` - Raw SKILL.md: https://api.skillmd.com/api/skills/onsager-ai/git-commit/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: onsager-ai (https://skillmd.com/u/onsager-ai) - Updated: 2026-09-09 - Page: https://skillmd.com/skills/onsager-ai/git-commit --- # Git Commit Write clean, atomic commits that communicate intent clearly. ## When to Use This Skill Activate when any of the following are true: - User asks to "commit", "make a commit", "stage changes", or "write a commit message" - User says "commit my changes" or "commit this" - A logical unit of work is complete and ready to land - User asks about `git add`, `git commit`, or `git amend` ## Decision Tree ``` What does the user need? Stage + commit changes? → Check what changed: git status + git diff --staged → Group related changes (atomic commit rule below) → Write message in conventional format → If hook fails: fix root cause, re-stage, new commit Amend the last commit? → ONLY if NOT yet pushed to remote → OK for: missing file, minor message fix, small oversight → New commit instead: substantial change, already pushed Write a commit message only? → Follow conventional format below → Lead with "why", not "what" Hook failure? → Read the full hook output → Fix the root cause — never use --no-verify ``` ## Conventional Commits Format ``` (): ← optional; explain *why*, not *what*