Slash command

/commit

Stages and commits with a clean conventional-commit message generated from the actual diff — no "update files" commits.

gitcommitworkflow

Install to

~/.claude/commands/commit.md

descriptionReview the staged + unstaged changes and create a well-formed commit.

Look at the current changes and create a commit:

Run git status and git diff (staged and unstaged) to see what changed.
Run git log --oneline -10 to match this repo’s message style.
Stage the relevant files by name (never git add -A blindly — skip .env, build artifacts, anything that looks like a secret).
Write a concise message: a type(scope): summary subject line under ~70 chars, then a body explaining the WHY if it isn’t obvious.
Commit. Do NOT push unless I ask.

If there are no changes, say so — don’t create an empty commit.

md · 15 lines

1---
2description: Review the staged + unstaged changes and create a well-formed commit.
3---
4
5Look at the current changes and create a commit:
6
71. Run `git status` and `git diff` (staged and unstaged) to see what changed.
82. Run `git log --oneline -10` to match this repo's message style.
93. Stage the relevant files by name (never `git add -A` blindly — skip
10   `.env`, build artifacts, anything that looks like a secret).
114. Write a concise message: a `type(scope): summary` subject line under
12   ~70 chars, then a body explaining the WHY if it isn't obvious.
135. Commit. Do NOT push unless I ask.
14
15If there are no changes, say so — don't create an empty commit.

How to install

Copy the code and save it to ~/.claude/commands/commit.md (user) or .claude/commands/commit.md (project).
Commands hot-reload — it's available in the current session immediately.
Run it by typing /commit in the prompt.
Verify: type / and look for it in the command list.

← More slash commands