git-commit

Claude Command: Commit (Git-only)

This command works without any package manager/build tools, using only Git to:

• Read changes (staged/unstaged)
• Determine if changes should be split into multiple commits
• Generate Conventional Commits style messages with optional emoji for each commit
• Execute git add and git commit as needed (runs local Git hooks by default; use --no-verify to skip)

---

Usage

/git-commit
/git-commit --no-verify
/git-commit --emoji
/git-commit --all --signoff
/git-commit --amend
/git-commit --scope ui --type feat --emoji

Options

• --no-verify: Skip local Git hooks (pre-commit/commit-msg etc.).
• --all: When staging area is empty, automatically git add -A to include all changes in the commit.
• --amend: Amend the last commit without creating a new one (preserves author and timestamp unless local Git config specifies otherwise).
• --signoff: Add Signed-off-by line (use when following DCO process).
• --emoji: Include emoji prefix in commit message (omit for plain text).
• --scope <scope>: Specify commit scope (e.g., ui, docs, api), written to message header.
• --type <type>: Force commit type (e.g., feat, fix, docs), overrides automatic detection.

Note: If the framework doesn't support interactive confirmation, enable confirm: true in front-matter to avoid mistakes.

---

What This Command Does

1. Repository/Branch Validation

   • Check if in a Git repository using git rev-parse --is-inside-work-tree.
   • Read current branch/HEAD status; if in rebase/merge conflict state, prompt to resolve conflicts first.

2. Change Detection

   • Get staged and unstaged changes using git status --porcelain and git diff.
   • If staged files = 0:
     • If --all is passed → Execute git add -A.
     • Otherwise prompt choice: continue analyzing unstaged changes for suggestions, or cancel to manually group staging.

3. Split Suggestions (Split Heuristics)

   • Cluster by concerns, file modes, change types (e.g., source code vs docs/tests; different directories/packages; additions vs deletions).
   • If multiple independent changesets or large diff detected (e.g., > 300 lines / across multiple top-level directories), suggest splitting commits with pathspecs for each group (for subsequent git add <paths>).