npx claudepluginhub acbcdev/claude-code --plugin git-mastergrouping strategy (files, features, modules, etc.)Use the @agent-commit-generator to create commits grouped according to your strategy in $ARGUMENTS. **Important:** Never include co-author information in commit messages. **Grouping examples:** default strategy is `files` - `files` - one commit per each file - `features` - one commit per each feature touched across files - `domain` - group by each business domain (auth, payments, etc.) - `modules` - organize by each code module or component **Process:** 1. Specify in $ARGUMENTS how to group changes: "files", "features", "modules", "domain", etc. 2. The agent analyzes staged changes an...
/commitStages 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.
/commitStages 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.
/commitCreates 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.
/commitCreates 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.
/commitRuns 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.
/commitAnalyzes current git diff, generates 3 conventional commit message options (concise, detailed, comprehensive), presents for user selection, and executes git commit.
Use the @agent-commit-generator to create commits grouped according to your strategy in $ARGUMENTS.
Important: Never include co-author information in commit messages.
Grouping examples:
default strategy is files
files - one commit per each filefeatures - one commit per each feature touched across filesdomain - group by each business domain (auth, payments, etc.)modules - organize by each code module or componentProcess:
Do NOT add these lines to your commits:
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Your commits should reflect your work and authorship. Write clean, meaningful commit messages without any tool signatures or references.
feat(auth): add login feature
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
feat(auth): add login feature
Implement user authentication with JWT tokens and secure password hashing.
- Add login endpoint
- Implement JWT token generation
- Add password validation
When committing related changes across multiple files:
feat(api): implement user profile endpoints
Add endpoints for retrieving and updating user profiles.
- GET /api/users/:id - retrieve user profile
- PUT /api/users/:id - update user profile
- Implement validation for profile fields
- Add database migrations for profile fields
- Write tests for new endpoints