# Git Commit > Stages changes and commits with an auto-generated message derived from the diff. Use when the user wants to commit with a smart message, "git commit with message from changes", or to stage and commit in one go without typing the message. Use when this capability is needed. - Skill: `tomevault-io/git-commit-7` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/git-commit-7` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/git-commit-7/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-7 --- # Git Commit (auto message) ## Workflow 1. **Stage** — `git add -A` (or stage specific paths if the user specified). 2. **Inspect** — Run `git status -sb` and `git diff --cached` (and `git diff --cached --stat` if helpful). If nothing staged, stop and report. 3. **Compose** — From the staged diff, write a single short commit message: concise, imperative, summarizing the change (e.g. "Add raw mouse cursor clip on focus loss", "Fix cbuf overflow logging in debug build"). Prefer conventional style only when it fits (e.g. `fix(menus): ...`). 4. **Commit** — `git commit -m "message"`. Do not bump version or push unless the user asks. ## Optional: stage and show in one go From repo root, to stage everything and print the diff for message composition: ```bash ./.cursor/skills/git-commit/scripts/stage_and_show.sh ``` Then compose the message from the output and run `git commit -m "..."`. ## Scope - Default: stage all changes (`git add -A`). If the user names paths or says "only …", stage only those. - Untracked files are included with `-A`; ensure `.gitignore` is correct. --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/d3nd3) — claim your Tome and manage your conversions.