From ai-commit-gen
Analyzes git diff to generate conventional commit messages with type, scope, subject, body, and footer. Presents three options (concise, detailed, comprehensive) and commits the chosen message.
How this command is triggered — by the user, by Claude, or both
Slash command
/ai-commit-gen:commitclaude-sonnet-4-5-20250929The summary Claude sees in its command listing — used to decide when to auto-load this command
You are an expert at analyzing code changes and writing clear, conventional commit messages. # Mission Analyze the current git diff and generate a professional conventional commit message following best practices. # Process ## 1. Check Git Status If there are no changes staged or unstaged, inform the user: ## 2. Analyze Changes Get both staged and unstaged changes: If there are only staged changes: ## 3. Analyze the Diff Look for: - **Type of change**: feat, fix, docs, style, refactor, perf, test, build, ci, chore - **Scope**: Which part of the codebase (optional but recommende...
You are an expert at analyzing code changes and writing clear, conventional commit messages.
Analyze the current git diff and generate a professional conventional commit message following best practices.
git status
If there are no changes staged or unstaged, inform the user:
No changes to commit. Stage your changes with:
git add <files>
Get both staged and unstaged changes:
git diff HEAD
If there are only staged changes:
git diff --cached
Look for:
feat: New feature or functionalityfix: Bug fixdocs: Documentation onlystyle: Code style/formatting (no logic change)refactor: Code restructuring (no behavior change)perf: Performance improvementtest: Adding/updating testsbuild: Build system changesci: CI/CD changeschore: Maintenance tasksFormat:
<type>(<scope>): <subject>
<body>
<footer>
Subject (required):
Body (optional but recommended):
Footer (if applicable):
BREAKING CHANGE: descriptionCloses #123, Fixes #456Show the user 3 commit message options:
Option 1: Concise (subject only)
feat(api): add user authentication endpoint
Option 2: Detailed (with body)
feat(api): add user authentication endpoint
Implement JWT-based authentication with email/password login.
Includes password hashing with bcrypt and token refresh logic.
Option 3: Comprehensive (with body and footer)
feat(api): add user authentication endpoint
Implement JWT-based authentication with email/password login.
Includes password hashing with bcrypt and token refresh logic.
Closes #42
Ask the user which option they prefer (1, 2, or 3), or if they want to customize.
Once confirmed, commit with:
git commit -m "<commit message>"
If the commit includes multiple files across different areas, consider suggesting to split into multiple commits.
Diff: Fix null pointer in user service
fix(auth): handle null user in validation
Previously crashed when user was null. Now returns proper
error message and 401 status code.
Fixes #89
Diff: Added dashboard charts
feat(dashboard): add analytics charts
Implement revenue and user growth charts using Chart.js.
Includes real-time updates via WebSocket connection.
Diff: Updated README
docs(readme): add installation instructions
Include step-by-step setup guide with prerequisites
and troubleshooting section.
Diff: Changed API response format
feat(api): standardize response format
Wrap all responses in {data, error, metadata} structure
for consistency across endpoints.
BREAKING CHANGE: All API responses now use new format.
Update clients to access data via response.data field.
If user provides custom message with the command:
/commit "fix: resolve login bug"
Skip analysis and commit directly with their message.
Amend last commit (if requested):
git commit --amend -m "<new message>"
Sign commit (if GPG configured):
git commit -S -m "<message>"
Empty commit (for CI triggers):
git commit --allow-empty -m "<message>"
If commit fails:
🔍 Analyzing changes...
Found changes in:
- src/auth/user.service.ts
- tests/auth.test.ts
📝 Generated commit messages:
Option 1 (Concise):
feat(auth): add user authentication
Option 2 (Detailed):
feat(auth): add user authentication
Implement JWT-based authentication with email/password login.
Includes password hashing and token refresh logic.
Option 3 (Comprehensive):
feat(auth): add user authentication
Implement JWT-based authentication with email/password login.
Includes password hashing and token refresh logic.
Closes #42
Which option? (1/2/3 or 'custom'):
After user selects, commit and show:
✅ Committed successfully!
Commit: abc1234
Message: feat(auth): add user authentication
18plugins reuse this command
First indexed Dec 31, 2025
Showing the 6 earliest of 18 plugins
npx claudepluginhub ktiseos-nyx/claude-code-plugins-plus-skills --plugin ai-commit-gen/commitAnalyzes git diff to generate conventional commit messages with type, scope, subject, body, and footer. Presents three options (concise, detailed, comprehensive) and commits the chosen message.
/commit-smartGenerates conventional commit messages by analyzing staged changes with AI, following type(scope): description format. Asks for confirmation before committing.
/commitAnalyzes git diffs or staged changes and generates conventional commit messages explaining the motivation behind the change. Also supports analyzing, staging, and validating commits.
/commitAnalyzes staged git changes and generates a conventional commit message with type, scope, subject, body, and footers.
/commit-msgGenerates a Conventional Commits-compliant commit message from staged changes. Accepts an optional scope argument.
/commitAnalyzes staged git changes and generates a structured Semantic Commit message, writing it to .git/COMMIT_EDITMSG for review and finalization.