Git Commit Rules
Execute git commit with conventional commit message analysis, intelligent staging, and message generation.
Enforces industry-standard Git practices, Conventional Commits, and automated pre-commit validation workflows.
Use when managing git workflow: creating branches, writing commit messages, preparing PRs, generating changelogs, managing releases…
Enforces disciplined Git workflows, atomic Conventional Commits, branch hygiene, and Pull Request lifecycles.
Keep git history clean and reviewable with branch naming, branch upkeep, merge conflict handling, and pull request prep.
Git history investigation. Use when: tracking code changes, finding where bugs were introduced, root cause analysis. Not for: code…
Git expert for atomic commits, rebasing, and history management with style detection
Use for any git operation (commit, push, pull, rebase, branch, PR, cherry-pick, etc.).
Detects git forge (GitHub/GitLab/Bitbucket) and maps CLI commands cross-platform.
Create commits, push branches, open pull requests (gh or manual), and update changelogs with PR numbers.
Push the current branch to origin and open a draft PR/MR with title derived from commit history and body listing every commit since the…
Safely stage, commit, and push intended git changes with conventional commit messages.
MANDATORY: Use instead of `git rebase` - provides automatic backup and conflict recovery
Diagnoses and safely fixes bugs in Git repositories using isolated worktrees with strict code review and testing validation.
Git operations including worktrees, branching, and repository management
Stacked (dependent) pull request workflow.
Stage selected git hunks non-interactively by reusing the source workflow under `claude/git-stage-hunk`.
Use when planning git branching strategies or managing branches for development.
Use when planning commit strategies or determining when to commit changes.
Manages isolated Git worktrees and standardized topic branches across creation, merging, and cleanup lifecycles.