Commit craft

A small procedure for staging, splitting, and describing work so git history stays usable — including when Cursor made the edits.

Loaded on demand when the task matches the description.

Install path

.cursor/skills/commit-craft/SKILL.md

---
name: commit-craft
description: Stage and commit work in focused commits with accurate messages. Use when the user asks to commit, split a diff, or clean up git history.
---

# Commit craft

## Rules

- One concern per commit. Do not mix a rename, a feature, and a lockfile bump.
- Subject: imperative, specific. “Add pack zip API route” beats “updates.”
- Body only when the why is not obvious from the diff.
- Never invent co-authors. Never commit secrets, `.env`, or credentials.

## Steps

1. Read `git status` and `git diff`.
2. Propose the split if there is more than one concern.
3. Stage the named paths. Do not `git add -A` unless the user asked.
4. Commit. Show the resulting `git log -1 --stat`.

## Don’t

- Rewrite published history unless asked.
- Use junk trailers or emoji as a substitute for a subject.