Slash Command

/commit

Analyzes local git changes, stages files excluding secrets, drafts Conventional Commits message, confirms with user, and commits locally.

Git

code-quality

From claude-scholar

Install

Run in your terminal

npx claudepluginhub galaxy-dawn/claude-scholar --plugin claude-scholar

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

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

commands-version-control-git

2.7k

/commit

BashReadGlob

all-commands

2.7k

/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

/commit

Runs git checks, lint/typecheck/tests, code review, then creates conventional commit message and commits staged changes. Supports --no-verify, --amend, --push flags.

pro-workflow

1.5k

/commit

Creates a conventional git commit with auto-generated message from staged changes. Supports types like feat, fix; accepts optional scope or message hint.

Bash(git status:*)Bash(git diff:*)Bash(git add:*)+1

project-starter

1.3k

Stats

Stars3068

Forks261

Last CommitFeb 11, 2026

Actions

View Source View Plugin View on GitHub View README

Tags

Instructions

Check Git Status

Run git status to review all changes
Run git diff to inspect modifications

Analyze Changes

Review changed files and their content
Determine commit type and scope
Draft a concise commit message

Commit Type Reference

feat     - New feature
fix      - Bug fix
docs     - Documentation only
style    - Code style (formatting, semicolons, etc.)
refactor - Code refactoring (no feature/fix)
perf     - Performance improvement
test     - Adding or updating tests
chore    - Build, CI, tooling, dependencies

Commit Message Format

<type>(<scope>): <subject>

<body>

Co-Authored-By: Claude <noreply@anthropic.com>

Subject: imperative mood, no period, max 72 chars
Body: explain what and why (optional for small changes)
Scope: affected module (data, model, config, trainer, utils, workflow)

Stage and Commit

Stage relevant files with git add
Do NOT stage files containing secrets (.env, credentials, tokens)
Create commit with formatted message
Verify with git log --oneline -1

Commit

Stage and commit changes using Conventional Commits format.

Instructions

Check Git Status
- Run git status to review all changes
- Run git diff to inspect modifications
Analyze Changes
- Review changed files and their content
- Determine commit type and scope
- Draft a concise commit message

Commit Type Reference

feat     - New feature
fix      - Bug fix
docs     - Documentation only
style    - Code style (formatting, semicolons, etc.)
refactor - Code refactoring (no feature/fix)
perf     - Performance improvement
test     - Adding or updating tests
chore    - Build, CI, tooling, dependencies

Commit Message Format
```
<type>(<scope>): <subject>

<body>

Co-Authored-By: Claude <noreply@anthropic.com>
```
- Subject: imperative mood, no period, max 72 chars
- Body: explain what and why (optional for small changes)
- Scope: affected module (data, model, config, trainer, utils, workflow)
Stage and Commit
- Stage relevant files with git add
- Do NOT stage files containing secrets (.env, credentials, tokens)
- Create commit with formatted message
- Verify with git log --oneline -1

Notes

This command only commits locally. Use /update-github to also push.
Always confirm the commit message with the user before committing.
If unsure about type or scope, ask the user.