Stats
Actions
Tags
How this command is triggered — by the user, by Claude, or both
Slash command
/hafley:git-commitFiles this command reads when invoked
This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /git-commit ## Steps 1. Run `git status` and `git diff --cached --stat` to see what's staged. If nothing is staged, show status and ask what to add. 2. Run `git log --oneline -5` to match the repo's commit message style. 3. Write the commit message as a heredoc. Format: Three layers, in order: - **Facts**: what the diff does and why, readable by anyone with no context on who did what - **Human**: the decisions, design calls, corrections, and direction the human provided - **AI**: what Claude actually executed to implement those decisions 4. Commit: One commit call. No interactive ...
git status and git diff --cached --stat to see what's staged. If nothing is staged, show status and ask what to add.git log --oneline -5 to match the repo's commit message style.<short summary line>
<what changed and why -- plain factual description of the diff, no attribution>
Directed by: <what the human decided, requested, or designed>
Implemented by: Claude -- <what was coded, configured, or wired up>
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Three layers, in order:
git commit -m "$(cat <<'EOF'
...
EOF
)"
One commit call. No interactive flags. No --amend unless explicitly asked.
npx claudepluginhub hafley66/claude-research --plugin hafley/git-commitCreates a git commit following the GAAC tag format, automatically inferring L1/L2 component tags from changed file paths and extracting issue references from branch names.
/git-commitAnalyzes Git changes, categorizes them, generates Conventional Commits message with Chinese description, adds relevant files, commits, and reports files, message, and hash.
/git-commitCreates conventional git commits with emojis, auto-stages unstaged files if needed, analyzes diffs, detects multiple logical changes, and suggests splitting into atomic commits.