Slash Command

/commit

From rpi

Reviews session changes with git status/diff, plans atomic commits with descriptive messages, proposes to user, and executes git add/commit upon confirmation.

Git

git-workflow

Install

npx claudepluginhub hoblin/claude-ruby-marketplace --plugin rpi

Prompt Preview

# Commit Changes

You are tasked with creating git commits for the changes made during this session.

## Process:

1. **Think about what changed:**
   - Review the conversation history and understand what was accomplished
   - Run `git status` to see current changes
   - Run `git diff` to understand the modifications
   - Consider whether changes should be one commit or multiple logical commits

2. **Plan your commit(s):**
   - Identify which files belong together
   - Draft clear, descriptive commit messages
   - Use imperative mood in commit messages
   - Focus on why the changes were mad...

Command Content

Other plugins with /commit

/commit

Stages unstaged changes based on git status and diff analysis, then creates a commit with a generated message. Uses current branch and recent commit history for context.

Bash(git add:*)Bash(git status:*)Bash(git commit:*)

commit-commands

15.9k

/commit

Stages changes and commits locally using Conventional Commits format. Analyzes git status/diffs, drafts typed message with scope, confirms with user before git add and commit.

claude-scholar

3.4k

/commit

Creates well-formatted git commits with conventional messages and emojis. Runs pre-commit checks (lint/format/build/docs), auto-stages files if needed, analyzes diffs, and suggests splitting multi-change commits unless --no-verify.

BashReadGlob

all-commands

2.7k

/commit

BashReadGlob

commands-version-control-git

2.7k

/commit

Runs pre-commit git checks, quality gates (lint, typecheck, tests), code review for issues; drafts conventional commit message; stages specific files and commits. Supports --no-verify, --amend, --push options.

pro-workflow

1.9k

/commit

Analyzes current git diff, generates 3 conventional commit message options (concise, detailed, comprehensive), presents for user selection, and executes git commit.

claude-sonnet-4-5-20250929

ai-commit-gen

1.9k

Stats

Parent Repo Stars24

Parent Repo Forks1

Last CommitJan 6, 2026

Used By4 plugins

Actions

View Source View Plugin View on GitHub View README

Tags

# Commit Changes You are tasked with creating git commits for the changes made during this session. ## Process: 1. **Think about what changed:** - Review the conversation history and understand what was accomplished - Run `git status` to see current changes - Run `git diff` to understand the modifications - Consider whether changes should be one commit or multiple logical commits 2. **Plan your commit(s):** - Identify which files belong together - Draft clear, descriptive commit messages - Use imperative mood in commit messages - Focus on why the changes were mad...

Commit Changes

You are tasked with creating git commits for the changes made during this session.

Process:

Think about what changed:

Review the conversation history and understand what was accomplished
Run git status to see current changes
Run git diff to understand the modifications
Consider whether changes should be one commit or multiple logical commits

Plan your commit(s):

Identify which files belong together
Draft clear, descriptive commit messages
Use imperative mood in commit messages
Focus on why the changes were made, not just what

Present your plan to the user:

List the files you plan to add for each commit
Show the commit message(s) you'll use
Ask: "I plan to create [N] commit(s) with these changes. Shall I proceed?"

Execute upon confirmation:

Use git add with specific files (never use -A or .)
Create commits with your planned messages
Show the result with git log --oneline -n [number]

Important:

NEVER add co-author information or Claude attribution

Commits should be authored solely by the user

Do not include any "Generated with Claude" messages

Do not add "Co-Authored-By" lines

Write commit messages as if the user wrote them

Remember:

You have the full context of what was done in this session

Group related changes together

Keep commits focused and atomic when possible

The user trusts your judgment - they asked you to commit

Commit Changes

You are tasked with creating git commits for the changes made during this session.

Process:

Think about what changed:
- Review the conversation history and understand what was accomplished
- Run git status to see current changes
- Run git diff to understand the modifications
- Consider whether changes should be one commit or multiple logical commits
Plan your commit(s):
- Identify which files belong together
- Draft clear, descriptive commit messages
- Use imperative mood in commit messages
- Focus on why the changes were made, not just what
Present your plan to the user:
- List the files you plan to add for each commit
- Show the commit message(s) you'll use
- Ask: "I plan to create [N] commit(s) with these changes. Shall I proceed?"
Execute upon confirmation:
- Use git add with specific files (never use -A or .)
- Create commits with your planned messages
- Show the result with git log --oneline -n [number]

Important:

NEVER add co-author information or Claude attribution
Commits should be authored solely by the user
Do not include any "Generated with Claude" messages
Do not add "Co-Authored-By" lines
Write commit messages as if the user wrote them

Remember:

You have the full context of what was done in this session
Group related changes together
Keep commits focused and atomic when possible
The user trusts your judgment - they asked you to commit