git-commit

Git Commit

Write a commit message for the current changes and commit it. The message MUST match the style already used in this repo — do NOT default to any particular format.

Hard rules

• Commit without asking. Pick the single best message and create the commit — no options, no confirmation gate. The user amends or resets afterwards if the message is wrong, which is cheaper than a round trip on every commit.
• Only commit what the change is about. Never git add -A blindly. Stage the files that belong to the change, and leave anything unrelated, generated, or secret-looking alone — say what you skipped.
• Keep the context small. This skill almost always runs at the end of a long session, where every extra round trip and every line of diff is re-sent along with the whole conversation. Gather in one call, bound the diff, and never re-run a command whose output you already have.

Steps

1. Gather the evidence — one call

Run all of it as a single command, not one tool call per fact:

git log --oneline -20
git status --short
git diff --cached --stat
ls -d commitlint.config.* .commitlintrc* 2>/dev/null
grep -l '"commitlint"' package.json 2>/dev/null

If the staged stat is empty, nothing is staged — the scope is the unstaged changes instead (git diff --stat), and every later --cached command below drops the flag to match.

From the log output, identify the repo's style:

• Whether messages use a prefix/type convention or are freeform
• Capitalization (sentence case vs lowercase)
• Tense and mood (imperative vs past tense)
• Use of scopes, tags, or ticket references
• Typical length and level of detail

If a commitlint config turned up, read it — its rules take precedence over what the log suggests.

2. Read the diff, bounded

The diff is the single largest thing this skill puts in context, and it stays there for every later call. Never pull in more of it than the message needs.

git diff --cached -- . ':(exclude)*.lock' ':(exclude)*-lock.json' ':(exclude)*.sum'