commit

Commit

Stage and commit all current workspace changes. Splits changes into logical commits when multiple unrelated concerns are present. Writes conventional commit messages for each group.

Input

$ARGUMENTS — optional freeform context or description to inform the commit message (e.g. "this fixes the login timeout issue"). If omitted, infer everything from the diff.

Conventional Commit Format

Every commit message must follow this format:

type(scope): description

Type Enum

• feat — new feature
• fix — bug fix
• chore — maintenance, dependency updates, no functional change
• refactor — code reorganization without behavior change
• docs — documentation changes
• test — test additions or changes
• style — formatting, no functional change

Subject Line

Keep the subject line (first line) under 72 characters.

Body

Add a body when the "why" isn't obvious from the diff:

• Blank line after subject
• Explain the motivation or reason for the change
• Wrap at 72 characters

Critical Constraints

NEVER mention Claude in any commit message. NEVER add "Co-Authored-By", "Co-Author", or any co-author attribution lines. These rules are absolute and override any other instructions.

Process

1. Inspect current state

Run these in parallel to understand what's changed:

git status
git diff --cached
git diff

2. Identify logical groupings

Examine the changed files and their diffs. Group files by concern — each group should represent a single logical change (e.g. a new feature, a bug fix, a dependency bump). If all changes belong to one concern, there is one commit. If multiple concerns are present, plan one commit per concern.

If $ARGUMENTS is provided, use it to inform the commit message subject and body.

3. For each group: stage, write message, commit

For each logical group, in order:

a. Stage the relevant files:

git add <file1> <file2> ...

To stage all remaining changes in one pass (only when grouping is complete):

git add -A

b. Write the commit message following the conventional commit format above.

c. Commit using HEREDOC syntax:

git commit -m "$(cat <<'EOF'
type(scope): short description under 72 chars

Optional body explaining the why, wrapped at 72 chars.
EOF
)"

Omit the body when the subject line is self-explanatory.

4. Confirm

After all commits are made, run:

git log --oneline -5

Report what was committed.

Constraints

• Never group unrelated changes into a single commit
• Never skip the HEREDOC syntax — it preserves newlines correctly
• Never add co-author lines or mention Claude
• Never amend an existing commit — always create new ones
• If git status is clean, report "Nothing to commit" and stop