Commit staged changes

Claude Code slash command (.claude/commands/commit.md). Writes a Conventional Commit message from the staged diff, matching repo history style, and commits after showing it.

License: CC0-1.0 · By waxmark · v1 · 2026-11-02

Share on X

Add a trust badge to your README

[![Waxmark](https://waxmark.app/api/badge/commit)](https://waxmark.app/items/commit/scan)
Report
---
description: Write a Conventional Commit message for the staged changes and commit them
argument-hint: [optional type/scope hint, e.g. "fix(auth)"]
allowed-tools: Bash(git status *), Bash(git diff *), Bash(git log *), Bash(git commit *)
disable-model-invocation: true
---

Create one commit from what is currently staged.

Staged files:
!`git diff --cached --stat`

Staged diff:
!`git diff --cached`

Recent commit subjects (match their style):
!`git log --oneline -12`

Hint from the user, if any: $ARGUMENTS

Steps:
1. If the staged diff is empty, stop and say nothing is staged. Do not stage files yourself.
2. Write a Conventional Commits message: `type(scope): subject` in imperative mood, subject at most 72 characters; a body wrapped at 72 columns explaining what and why when the change is not self-evident; `BREAKING CHANGE:` footer and `!` marker when applicable; `Closes #N` when the diff or hint names an issue. Use the type and scope vocabulary visible in the recent subjects. If the hint provides a type or scope, use it unless the diff contradicts it.
3. Show the full message in a fenced block.
4. Commit it using a heredoc so the body formatting survives:
   ```
   git commit -m "$(cat <<'EOF'
   <message>
   EOF
   )"
   ```
5. Print `git log -1 --stat` and stop. Do not push.

If the staged diff mixes unrelated changes (different types or scopes), commit nothing and propose a split with the `git add -p` or path list for each commit.
Commit staged changes · Waxmark