# Git Commits > Git commit workflow and message format. Use when making commits, asking about commit conventions, or after completing code changes. Enforces atomic commits with structured messages (type/scope/summary + what/why body). - Skill: `iamhenry/git-commits` (Agent Skill) - Install (CLI): `npx skillmds@latest add iamhenry/git-commits` - Raw SKILL.md: https://api.skillmd.com/api/skills/iamhenry/git-commits/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Productivity - Author: iamhenry (https://skillmd.com/u/iamhenry) - Updated: 2026-09-10 - Page: https://skillmd.com/skills/iamhenry/git-commits --- # Git Commits ## WORKFLOW 1. Run command to see all modified files `git status --porcelain` 2. Run brief diff command to understand changes `git diff` 3. PRE-FLIGHT (before any commit): scan staged diff + filenames for sensitive info - What to look for: passwords, API keys, tokens, secrets, private keys, credentials, personal data (emails, phone numbers, names of private individuals), logs, screenshots, session data - Scan the diff (`git diff` / `git diff --cached`) AND filenames (e.g. `debug.log`, `screenshot.png`, `notes.txt`) - Also check untracked files about to be committed - If anything sensitive found: STOP, report it, ask the user. Never commit and "fix later". Git history keeps secrets forever. - If clean: proceed 4. Commit ALL (skip staging) using commit format below 5. Push changes 6. Then stop ## Format ``` ():

``` - Title (first line): Required - follows `():

` format - Body (after blank line): REQUIRED - for each changed file, add a parent bullet with the file path, then nested bullets for what changed and why. ## Example ``` ():

src/components/button.js - What: Added Button with size props. - Why: Enable dynamic size adjustments for a customizable UI. tests/button.test.js - What: Created tests for Button sizing. - Why: Ensure reliable rendering and detect regressions. ``` ## SCOPE Specifies area of change: - auth, user, dashboard, api, database, ui, transfer, etc. ## ANTI-PATTERNS - NEVER skip the body - it documents intent