Slash Command

/commit

Create git commits for session changes with clear, atomic messages

npx claudepluginhub ii-vo/claude-meta

Allowed Tools

Bash

Prompt Preview

# Commit Changes

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

## Current State





## Process:

1. **Think about what changed:**

    - Review the conversation history and understand what was accomplished
    - Use the git status/diff output above 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 prefixes on the commit messages; fix, refactor, feat, docs, style,...

Command Content

Other plugins with /commit

/commit

15.9k

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.

3 tools

commit-commands

/commit

3.5k

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

/commit

2.7k

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.

3 tools

commands-version-control-git

/commit

2.7k

3 tools

all-commands

/commit

2.0k

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

/commit

1.9k

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

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitDec 29, 2025

Actions

View Source View Plugin View on GitHub View README

# Commit Changes You are tasked with creating git commits for the changes made during this session. ## Current State ## Process: 1. **Think about what changed:** - Review the conversation history and understand what was accomplished - Use the git status/diff output above 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 prefixes on the commit messages; fix, refactor, feat, docs, style,...

Commit Changes

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

Current State

!git status --short

!git diff --stat

Process:

Think about what changed:

Review the conversation history and understand what was accomplished
Use the git status/diff output above 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 prefixes on the commit messages; fix, refactor, feat, docs, style, test
Use imperative mood in commit messages
Focus on why the changes were made, not just what

Execute upon confirmation:

Use git add with specific files (never use -A or .)
Never commit dummy files, test scripts, or other files which you created or which appear to have been created but which were not part of your changes or directly caused by them (e.g. generated code)
ALWAYS commit .claude/sessions/ directory - session data must always be committed
DO commit .claude/ directory contents including sessions, commands, hooks, skills, and settings
DO commit thoughts/ directory (plans/, handoffs/, research/, prs/)
DO commit public/ assets (logos, icons, images)
DO NOT commit .claude/settings.json.backup.* temporary backup files
Create commits with your planned messages until all of your changes are committed with git commit -m

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

IMPORTANT: - never stop and ask for feedback from the user.

Commit Changes

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

Current State

!git status --short

!git diff --stat

Process:

Think about what changed:
- Review the conversation history and understand what was accomplished
- Use the git status/diff output above 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 prefixes on the commit messages; fix, refactor, feat, docs, style, test
- Use imperative mood in commit messages
- Focus on why the changes were made, not just what
Execute upon confirmation:
- Use git add with specific files (never use -A or .)
- Never commit dummy files, test scripts, or other files which you created or which appear to have been created but which were not part of your changes or directly caused by them (e.g. generated code)
- ALWAYS commit .claude/sessions/ directory - session data must always be committed
- DO commit .claude/ directory contents including sessions, commands, hooks, skills, and settings
- DO commit thoughts/ directory (plans/, handoffs/, research/, prs/)
- DO commit public/ assets (logos, icons, images)
- DO NOT commit .claude/settings.json.backup.* temporary backup files
- Create commits with your planned messages until all of your changes are committed with git commit -m

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
IMPORTANT: - never stop and ask for feedback from the user.