# Git Commit Message

> Formulate a git commit message. Use this skill whenever asked to create a commit message. Use when this capability is needed.

- Skill: `tomevault-io/git-commit-message-2` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/git-commit-message-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/git-commit-message-2/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-message-2

---


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

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/bkircher) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-11 -->