# Commit > Staged changes - Skill: `steph-dove/commit` (Agent Skill) - Install (CLI): `npx skillmds@latest add steph-dove/commit` - Raw SKILL.md: https://api.skillmd.com/api/skills/steph-dove/commit/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: steph-dove (https://skillmd.com/u/steph-dove) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/steph-dove/commit --- ## Staged changes ```! git diff --cached --stat ``` ```! git diff --cached ``` ## Recent commit style ```! git log --oneline -10 ``` ## Current branch ```! git branch --show-current ``` ## Instructions Write a commit message for the changes shown above. Read CLAUDE.md for any project-specific commit conventions before writing. Format: ``` (): ``` Types: feat, fix, refactor, test, docs, chore, style, perf Scope: the area of code affected (e.g. auth, api, ui) Rules: - Summary line under 72 characters. - Body wraps at 80 characters. - Match the style of the recent commits shown above. - Focus on "why" in the body, not "what" (the diff already shows "what"). - **Skip the body when the subject already says it.** A rename, a version bump, a typo fix needs one line. Write a body only when there's a why the subject can't carry, and keep it to a sentence or two. - If the branch name has a ticket reference (e.g. FEAT-1234), include it in the body. {{HUMANIZE}} Output ONLY the commit message, nothing else. Do not wrap it in code blocks. ## When NOT to use - The user wants to actually run `git commit` — this skill only writes the message text. - Nothing is staged — ask the user to stage changes first instead of inventing a message. - The user wants a commit message for unstaged or unmerged changes — point them at `git add` first.