# Git Commit

> Write clear conventional commit messages and group related changes into focused commits.

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

---


# Git Commit

Use when preparing commits or summarizing a changeset for version control.

## When to activate

- User asks to commit changes
- Reviewing staged diff before commit
- Splitting a large diff into logical commits

## Procedure

1. Read the full diff; identify distinct logical changes.
2. Use conventional commits: `feat:`, `fix:`, `refactor:`, `docs:`, `test:`, `chore:`.
3. Subject line ≤ 72 chars; body explains why, not just what.
4. One concern per commit; avoid mixing unrelated files.
5. Never commit secrets, `.env`, or credentials.

## Output format

```
feat(scope): short subject

Optional body explaining motivation and trade-offs.
```