# Git Commit Message

> Formulate a git commit message. Use this skill whenever asked to create a commit message.

- Skill: `zuoguyoupan2023/git-commit-message` (Agent Skill)
- Install (CLI): `npx skillmds@latest add zuoguyoupan2023/git-commit-message`
- Raw SKILL.md: https://api.skillmd.com/api/skills/zuoguyoupan2023/git-commit-message/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: zuoguyoupan2023 (https://skillmd.com/u/zuoguyoupan2023)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/zuoguyoupan2023/git-commit-message

---


Create a commit message summarizing the changes just made. Only take staged changes into account.

<important>
Follow The seven rules of a great Git commit message (https://cbea.ms/git-commit/#seven-rules) to the letter.
</important>

## Scan for what is staged

Use the context to construct a good message but make sure to only address the scope that is currently staged in git.

List files that are staged (in the index):
<command>
git diff --cached --name-only
</command>

Show the full diff of staged changes:
<command>
git diff --cached
</command>

## Rules

1. Separate subject from body with a blank line
2. Limit the subject line to 50 characters
3. Capitalize the subject line
4. Do not end the subject line with a period
5. Use the imperative mood in the subject line
6. Wrap the body at 72 characters
7. Use the body to explain what and why vs. how