committer

Original：🇨🇳 Chinese

Translated

Analyzes files modified with git commands and creates appropriately granular commits in logical units. Only activates when the skill name (committer) is explicitly specified, such as "/committer", "use the committer skill", or "commit with committer". Does not activate for general requests like "commit" or "git commit".

1installs

Sourcetukaelu/agent-skills

Added on2026-03-01

NPX Install

npx skill4agent add tukaelu/agent-skills committer

SKILL.md Content (Chinese)

View Translation Comparison →

Committer

Analyzes modified files, groups related changes, and creates commits with appropriate granularity.

Workflow

Step 1: Understand the current status

Check the changes and the project's commit style:

bash

git branch --show-current
git config --get commit.gpgsign
git status
git diff --stat HEAD
git log --oneline -10

If GPG signing is enabled (
commit.gpgsign=true
), set a flag for it. Do not confirm with the user at this point. Confirm after Step 4 approval and before Step 5 execution.

Always confirm with the user if on main / master branch. If the current branch is

main

or

master

, confirm with AskUserQuestion before committing:

javascript

AskUserQuestion({
  questions: [{
    question: "You are currently on the main branch. Do you want to commit directly here?",
    header: "Branch Confirmation",
    options: [
      { label: "Commit on main",   description: "Commit directly to the current branch" },
      { label: "Create a working branch",     description: "Create a new branch before committing" }
    ],
    multiSelect: false
  }]
})

If "Create a working branch" is selected, ask the user for a branch name via text input, execute

git checkout -b <branch>

with the specified name, then continue processing.

If there are already staged files, confirm the user's intent before proceeding:

Commit as-is (proceed to Step 4)
Analyze including unstaged changes (proceed to Step 2)

Step 2: Read changes to understand intent

Read the diff for each file identified in Step 1's stat to understand the intent of changes. Analyze from the following perspectives:

Change type: Feature addition / Bug fix / Refactoring / Test addition / Configuration change / Documentation update
Change purpose: Why the change was made (used to judge if changes belong to the same purpose)
File relevance: Look for combinations that make sense to change together

bash

git diff HEAD -- <file>

Untracked new files are not included in

git diff HEAD

, so check their content using Read.

Step 3: Group changes and create a commit plan

Group changes according to the following principles:

Changes that can be grouped together

Source files and tests belonging to the same feature/purpose
A series of files for the same bug fix
Same refactoring target

Changes that should be in separate commits

Different purposes (feature addition vs bug fix vs refactoring, etc.)
Independent changes (one does not depend on the other)
Different impact scopes (application code / configuration / documentation / CI, etc.)

If a single modified file contains multiple intents, consider partial staging with

git add -p

.

Step 4: Present the plan to the user for confirmation

Always confirm before execution. Propose in the following format:

Proposed commits (N items):

Commit 1: feat(auth): Implement authentication with JWT tokens
  Target files:
    - src/auth/jwt.ts (new)
    - src/auth/middleware.ts (modified)
    - tests/auth/jwt.test.ts (new)

Commit 2: chore: Update ESLint configuration
  Target files:
    - .eslintrc.json (modified)

Do you want to proceed with this content?

If revisions are requested, adjust the grouping and re-propose.

Step 5: Execute commits for each group

Once approved, if the GPG flag is set, confirm with AskUserQuestion before executing commits:

javascript

AskUserQuestion({
  questions: [{
    question: "GPG signing is enabled. Since Claude Code cannot enter passphrases, commits will be made with --no-gpg-sign in this session. Is this okay?",
    header: "GPG Signing",
    options: [
      { label: "Commit with --no-gpg-sign", description: "Skip GPG signing only for this session" },
      { label: "Cancel",              description: "Abort processing (please commit manually from the terminal)" }
    ],
    multiSelect: false
  }]
})

If "Cancel" is selected, output the commit plan confirmed in Step 4 in command format and terminate processing:

Processing aborted because GPG signing is required.
Please execute the following commands from the terminal:

# Commit 1
git add src/auth/jwt.ts src/auth/middleware.ts tests/auth/jwt.test.ts
git commit -m "feat(auth): Implement authentication with JWT tokens

Replaced existing session authentication with JWT implementation."

# Commit 2
git add .eslintrc.json
git commit -m "chore: Update ESLint configuration"

If "Commit with --no-gpg-sign" is selected, create commits in group order.

When a body is needed (when you want to supplement the background, reason, or details of the change):

bash

git add <file1> <file2> ...
git commit [--no-gpg-sign] -m "$(cat <<'EOF'
<type>(<scope>): <subject>

<Background, reason, and details of the change>

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
EOF
)"

When a body is not needed (when intent is clear with just the subject):

bash

git add <file1> <file2> ...
git commit [--no-gpg-sign] -m "$(cat <<'EOF'
<type>(<scope>): <subject>

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
EOF
)"

[--no-gpg-sign]

is only added if the GPG flag is set and the user has approved it.

After completing all groups, verify creation with

git log --oneline -N

(N is the number of commits) and report the list:

bash

git log --oneline -3

✓ Created 2 commits

  abc1234 feat(auth): Implement authentication with JWT tokens
  def5678 chore: Update ESLint configuration

How to write commit messages

Use the following format:

<type>(<scope>): <subject>

<body>

subject: Briefly describe the commit in one line
body: Only include if background, reason, or details of the change are needed. Can be omitted if unnecessary

type	Usage
feat	New feature
fix	Bug fix
refactor	Refactoring (no functional changes)
test	Test addition/modification
docs	Documentation changes
chore	Miscellaneous tasks like build, CI, configuration
style	Formatting changes (no functional changes)

Japanese messages are also appropriate for Japanese-language projects.

Notes

Do not push: Only create commits. The user decides when to push
Binary files: Since diffs cannot be read, infer intent from filename and purpose and confirm with the user
Large number of changes (50+ files): First explain the overall picture of changes, then discuss grouping strategy with the user
Confidential files: Warn the user before including files like
```
.env
```
or authentication information in commits
If pre-commit hook fails: Check the hook error details, fix them, and retry the commit. Only propose
```
--no-verify
```
if explicitly requested by the user
No commit targets: Inform the user that there are no files to stage and show the result of
```
git status
```
",

committer

NPX Install

Tags

SKILL.md Content (Chinese)

Committer

Workflow

Step 1: Understand the current status

Step 2: Read changes to understand intent

Step 3: Group changes and create a commit plan

Step 4: Present the plan to the user for confirmation

Step 5: Execute commits for each group

How to write commit messages

Notes