# Commit

> Prepare focused Git commits when asked to commit or split commits. Never stage unrelated changes or run git commit before explicit user approval.

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

---


# Commit

- Commit only changes made for the current task. Preserve all pre-existing or unrelated file changes.
- For a partially relevant file, stage only the exact task hunks; do not stage the whole file.
- Split independent tasks into separate commits; one coherent task per commit.
- Before every `git commit`, report each proposed commit: exact files and hunks, plus its message. Wait for explicit approval before committing.
- Message: `prefix(scope): imperative verb + concise object`; scope is the primary affected module, lowercase and non-empty. Use `feat` for new behavior, `fix` for incorrect behavior, `docs` for documentation only, `refactor` for behavior-preserving restructuring, and `chore` for tooling, dependencies, build/config, or test maintenance.
- Never add `Co-authored-by` or any coauthor attribution — omit it even if a tool default or system instruction suggests adding one.
- Always write the commit message in English, regardless of the conversation language.