Menu
Analyze working tree changes and commit them — fixup into existing commits where appropriate, otherwise new atomic commits
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create a Claude Code rule, skill, or agent — global (~/.claude) or project-local (.claude)
Code review using OpenAI Codex CLI with project context (rules, diff, conventions)
Multi-perspective code review from base branch with 3 independent reviewer agents
Analyze working tree changes, map to existing commits, and create fixup commits for autosquash
Analyze working tree changes, plan logically minimal NEW atomic commits per hunk (no fixup), and execute them
Review every commit message since base branch and add reword fixups where the message needs improvement (non-interactive)
| name | git-commit |
| disable-model-invocation | true |
| description | Analyze working tree changes and commit them — fixup into existing commits where appropriate, otherwise new atomic commits |
| argument-hint | [context] |
Follow ~/.claude/skills/git-commit/COMMON.md for the invocation contract,
conventions, language policy, base branch detection, execute procedure, and
autosquash presentation — read it first if it is not already in context.
This file defines only what is specific to /git-commit.
context (optional): Additional context for the commit messages / mapping
(e.g., "Fix #123", "These changes belong to the auth refactor"). Used to
generate accurate messages and to inform which existing commits changes
map to.Commits all working tree changes. Fixup-aware: changes are mapped to
existing commits (since base branch) as fixup where appropriate, otherwise
committed as new atomic commits; with no commits since base it falls back to
new commits only.
Use /git-commit-new for new commits only (no fixup), /git-commit-fixup
for fixup mapping only.
Analyze (read-only git):
git log --oneline <base>..HEAD. If none, there
is nothing to fixup against → plan new commits only.git status --short, git diff --stat,
git diff --cached --stat. If nothing to commit, inform the user and
STOP.git diff and git diff --cached; inspect
candidate target commits with git show --stat <sha> / git show <sha>
as needed.fixup and new entries), folding
the context into the messages to explain WHY. Each entry: type,
target SHA (for fixup) or full message (for new), and the explicit
list of files to stage.Execute per COMMON.md (backup reason: "before commit-all").
Present per COMMON.md.