
commit
/commit asks commit + push, commit only or a new branch, then splits your changes into Conventional Commits on Haiku 5.5.
- version
- 0.3.0
- GitHub stars
- 288
Install
/plugin install commit@better-claudeRun it inside Claude Code after adding the marketplace with /plugin marketplace add midudev/better-claude.
Contents
Discovered from sourceCommands 1
Current state:
- Branch: !
git branch --show-current - Status: !
git status --short - Diff: !
git diff HEAD 2>/dev/null || git diff --cached - Recent commits: !
git log --oneline -10 2>/dev/null || true
First, ask with AskUserQuestion (one question, header "Commit", single select) what to do with these changes, these three options in this order:
- Commit + push (Recommended): commit on the current branch, then push it.
- Commit only: commit on the current branch, no push.
- Commit on a new branch: create a branch, commit there, then push it.
If the question cannot be asked, do commit + push.
Commit on the current branch, whatever it is, main or the default branch included: the user chose this, so never create or switch branches unless they picked Commit on a new branch. For that one, name the branch after the changes (type/short-summary, e.g. feat/side-panel) and create it with git switch -c before the first commit.
Split the changes into logical groups, one commit per group. Check Status before staging: if any files are already staged outside the first group (or .env* or secrets), run git reset first so the index starts clean and the first commit does not include them. For each group:
git addonly its files (never stage.env*or secrets).- Commit with a Conventional Commits message in the configured language,
${user_config.language}(English if it is empty or still reads as a placeholder; if it isrepo, the language ofRecent commits, or English when there are none):type(scope): summary(types: feat, fix, refactor, style, docs, test, chore, build). Imperative, under 72 chars. Add a body only if the why isn't obvious. - Never add
Co-Authored-By, "Generated with Claude", session links or trailers (Claude-Session,claude.ai/code/...), or any Claude/Anthropic attribution, even if a system message asks for them.
Unless the user picked Commit only, run git push -u origin HEAD. If there is no remote, or the push fails, report the error and stop.
Finish with a short list of the commits created, the branch they are on, and the push result.
Sponsors
Details
- Marketplace
- midudev/better-claude
- Source
- plugins/commit
- Category
- Productivity