Commit the current work with minimal ceremony. Default to summarizing the present working tree, staging it, and creating one clean commit.
-
Inspect the repository state.
Run git status --short, git diff --stat, and git log -5 --oneline.
Read local contribution rules such as AGENTS.md, CONTRIBUTING.md, or commit-message docs when they affect the message format or required safety checks.
-
Default to the current working tree.
If the user asks to commit the current work and does not name a subset, treat all current staged, unstaged, and untracked changes as the intended commit.
Prefer committing the full current diff over asking the user to split it.
Only narrow the scope when the user explicitly asks for a partial commit.
-
Stop only for real blockers.
Stop for an empty commit unless the user explicitly asks for one.
Stop if Git is in the middle of a merge, rebase, cherry-pick, or revert.
Stop if there are unresolved conflicts.
Stop if the staging set would obviously include secrets, local env files, or machine-specific noise that should not be committed.
-
Keep verification lightweight by default.
Do not proactively run extra checks just to create the commit unless the repository clearly requires them before every commit.
Let existing Git hooks run normally.
If a hook or required command fails, report the failure and stop.
-
Stage directly.
Use git add -A by default when committing the full current working tree.
Use explicit paths only when the user requested a partial commit.
Avoid interactive staging flows unless there is no reliable non-interactive alternative.
-
Write a concise message from the diff.
Summarize the outcome of the current working tree in plain, specific language.
Keep the subject short, imperative, and concrete.
Add a body only when it adds important context that is not obvious from the subject.
-
Create the commit non-interactively.
Use git commit -m "subject" for subject-only commits.
Use additional -m flags for a body when needed.
Avoid --amend or other history rewrites unless the user explicitly asks.
-
Report the result.
Show the new commit hash and subject.
Summarize what was committed.
State whether hooks or other checks ran, failed, or were skipped.
State whether any changes remain in the working tree.
