# 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: `majiayu000/git-commits-6` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add majiayu000/git-commits-6` - Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/git-commits-6/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Productivity - Author: majiayu000 (https://skillmd.com/u/majiayu000) - Updated: 2026-09-09 - Page: https://skillmd.com/skills/majiayu000/git-commits-6 --- # 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. Commit ALL (skip staging) using commit format below 4. Push changes 5. 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