Intelligent git commit management with AI-powered message generation, staging analysis, and cleanup utilities.
Analyzes your current changes and creates a well-crafted git commit with an AI-generated message.
What it does:
- Analyzes both staged and unstaged changes
- Reviews recent commit history to match your repository's style
- Generates conventional commit messages (feat:, fix:, docs:, etc.)
- Provides detailed analysis before committing
- Always asks for approval before creating the commit
Usage:
/commit
/commit fixing authentication bug
/commit adding new user profile featureCleans up your git staging area by identifying and removing files that shouldn't be committed.
What it does:
- Scans staged files for common issues (build artifacts, IDE files, OS files, etc.)
- Identifies sensitive files (API keys, credentials, secrets)
- Recommends files to unstage
- Suggests .gitignore patterns to prevent future issues
- Safely removes or unstages files with your approval
Usage:
/cleanup # Analyze entire staging area
/cleanup dist/ # Clean up specific directory
/cleanup node_modules/ # Remove specific pathA specialized agent that handles the entire commit creation process with intelligence and care.
Capabilities:
- Deep analysis of code changes
- Context-aware commit message generation
- Conventional commit format support
- Multi-file change analysis
- Sensitive data detection
- Commit style consistency
How it works:
- Runs
git status,git diff, andgit logto gather context - Analyzes the nature and scope of changes
- Generates appropriate commit message following conventions
- Presents analysis and proposed message
- Waits for your approval before committing
This plugin is part of the claude-plugins marketplace. To install:
- Clone the marketplace repository
- Claude Code will automatically detect the plugin
- Commands and agents will be available immediately
- After making logical, cohesive changes
- When you want AI assistance crafting the perfect message
- To maintain consistent commit style across your team
- When unsure how to describe complex changes
- Before committing, to ensure you're not including unwanted files
- After bulk file operations that may have staged artifacts
- When you see files in
git statusthat shouldn't be there - To get recommendations for .gitignore improvements
The plugin follows Conventional Commits format:
<type>(<scope>): <subject>
<body>
<footer>
Common types:
feat: New featurefix: Bug fixdocs: Documentation changesstyle: Code style changes (formatting, missing semicolons, etc.)refactor: Code refactoringperf: Performance improvementstest: Adding or updating testschore: Maintenance tasksci: CI/CD changesbuild: Build system changes
# You: /commit
# Agent analyzes changes...
## Commit Analysis
**Files Changed**:
- src/components/UserProfile.tsx
- src/api/users.ts
- src/types/user.ts
**Change Type**: feat
**Scope**: user-profile
## Proposed Commit Message
feat(user-profile): add profile picture upload functionality
Implement image upload component with preview, validation, and
AWS S3 integration. Includes file size limits and format restrictions.
- Add ProfilePictureUpload component
- Integrate S3 presigned URL generation
- Add user avatar display in profile view
- Update user type definitions
## Changes Summary
Added complete profile picture upload feature with client-side validation,
S3 integration, and preview functionality.
Proceed with this commit?
# You: yes
# Agent commits with the message# You: /cleanup
## Staging Area Cleanup Analysis
### Currently Staged Files
- src/app.ts
- dist/bundle.js
- dist/bundle.js.map
- .DS_Store
- node_modules/.cache/webpack
- .env.local
### Recommended Removals
- dist/bundle.js: Build artifact (should not be committed)
- dist/bundle.js.map: Build artifact (should not be committed)
- .DS_Store: OS file (should not be committed)
- node_modules/.cache/webpack: Dependency cache (should not be committed)
- .env.local: SENSITIVE - Environment file with secrets!
### Suggested .gitignore Additions
dist/
.DS_Store
.env.local
node_modules/
Shall I unstage these files and update your .gitignore?- Review before committing: Always review the proposed commit message and make adjustments if needed
- Use descriptive context: When running
/commit [context], provide helpful context about your changes - Regular cleanup: Run
/cleanupperiodically to catch accidentally staged files - Learn from suggestions: The plugin's .gitignore recommendations help improve your repository hygiene
- Split commits: If the agent suggests your changes are too broad, consider splitting them into multiple commits
The plugin includes safety measures:
- Never commits without explicit approval
- Detects sensitive files (API keys, credentials, secrets)
- Warns about files matching sensitive patterns
- Recommends .gitignore patterns for security
Found an issue or have a suggestion? Please open an issue at: https://github.com/OneZeroCompany/claude-plugins
MIT License - See LICENSE file for details