AI-powered conventional commit message generator with smart analysis
Installation
npx claude-plugins install @jeremylongshore/claude-code-plugins-plus/git-commit-smart
Contents
Folders: commands, skills
Files: LICENSE, README.md
Documentation
AI-powered conventional commit message generator that analyzes your staged changes and creates professional, standardized commit messages automatically.
Features
- AI-Powered Analysis: Understands your code changes and generates contextual messages
- Conventional Commits: Follows the conventional commits standard automatically
- Fast Workflow: Generate commits in seconds with
/gcshortcut - Smart Categorization: Automatically determines commit type (feat, fix, docs, etc.)
- Breaking Change Detection: Identifies and documents breaking changes
- Interactive Confirmation: Review and edit before committing
Installation
# Add this marketplace to Claude Code
/plugin marketplace add jeremylongshore/claude-code-plugins
# Install the plugin
/plugin install git-commit-smart@claude-code-plugins-plus
Usage
Basic Usage
- Stage your changes:
git add .
- Generate commit message:
/commit-smart
# or use the shortcut:
/gc
- Review the generated message and confirm
Example Session
# Stage changes
git add src/auth/login.js src/api/users.js
# Generate commit
/gc
# Claude analyzes and proposes:
feat(auth): add OAuth2 Google login support
Implements Google OAuth2 authentication flow using Passport.js.
Users can now sign in with their Google account instead of
creating a new password.
Closes #123
# Commit with this message? (yes/no/edit)
yes
# Committed!
Commit Types
The plugin automatically selects the appropriate type:
feat: New featurefix: Bug fixdocs: Documentation onlystyle: Code style/formatting (no logic change)refactor: Code restructure (no behavior change)perf: Performance improvementtest: Adding/updating testschore: Maintenance tasks
Requirements
- Git repository with staged changes
- Claude Code editor
Configuration
No configuration needed! The plugin works out of the box.
Optional Context
You can provide additional context:
/gc - emphasize that this fixes a security vulnerability
Pro Tips
Stage related changes together - Commit logical units, not random files
Use the /gc shortcut - Saves typing and speeds up workflow
Review before committing - Always check the generated message makes sense
Add issue references - Plugin will detect and include “Closes #123” when appropriate
Break up large changes - Multiple focused commits are better than one massive commit
When NOT to Use
Merge commits - Use git’s default merge message instead
No staged changes - Stage changes first with git add
Emergency hotfixes - When you need to commit immediately without review
Troubleshooting
“No changes staged for commit”
Solution: Run git add <files> first to stage your changes
“Merge in progress detected”
Solution: For merge commits, use git commit --no-edit instead
Commit message too generic
Solution: Add more context when calling the command: /gc - this fixes the login bug
Examples
Bug Fix
fix(api): correct typo in email normalization
Changed tolowerCase() to toLowerCase() to fix TypeError
when processing user emails.
New Feature
feat(search): add global search functionality
Implements full-text search across products, users, and orders.
New SearchBar component provides real-time suggestions as user types.
Closes #45
Breaking Change
refactor(auth)!: change login to use email instead of username
BREAKING CHANGE: login() now requires email parameter instead of username.
Clients must update their authentication calls:
- Before: login(username, password)
- After: login(email, password)
License
MIT License - see LICENSE for details
Contributing
Contributions welcome! See CONTRIBUTING.md for guidelines.
Support
- Issues: GitHub Issues
- Discussions: GitHub Discussions
Made with ️ for developers who want better commit messages without the hassle
Included Skills
This plugin includes 1 skill definition:
generating-smart-commits
|
View skill definition
Git Commit Smart
This skill provides automated assistance for git commit smart tasks.
Prerequisites
Before using this skill, ensure:
- Git repository is initialized in {baseDir}
- Changes are staged using
git add - User has permission to create commits
- Git user name and email are configured
Instructions
- Analyze Staged Changes: Examine git diff output to understand modifications
- Determine Commit Type: Classify changes as feat, fix, docs, style, refactor, test, or chore
- Identify Scope: Extract affected module or component from file paths
- Detect Breaking Changes: Look for API changes, removed features, or incompatible modifications
- Format Message: Construct message following pattern:
type(scope): description - Present for Review: Show generated message and ask for confirmation before committing
Output
Generates conventional commit messages in this format:
type(scope): brief description
- Detailed explanation of changes
- Why the change was necessary
- Impact on existing functionality
BREAKING CHANGE: description if applicable
Examples:
feat(auth): implement JWT authentication middlewarefix(api): resolve null pointer exception in user endpointdocs(readme): update installation instructions
Error Handling
Common issues and solutions:
No Staged Changes
- Error: “No changes staged for commit”
- Solution: Stage files using
git add <files>before generating commit message
**Git Not In