Commit Message

Draft a high-quality commit message for the staged changes and create the commit.

Inputs you must gather first

Run these before drafting anything. Skipping them produces guesses, not messages.

git rev-parse --is-inside-work-tree
git status --short
git diff --staged --stat
git diff --staged
git log -n 20 --oneline

Use the recent log to learn the repository's own conventions (type vocabulary, scope style, casing) and follow them when they don't conflict with the rules below. If the log shows a clearly different style, prefer the repo's style and mention the deviation to the user once.

Staging behavior depends on what is already staged: