MANDATORY: Use instead of `git commit --amend` - verifies HEAD and push status first
Interact with GitHub and Gitea issue trackers and CI systems.
Enforces team git branching, commit messaging, and pull request conventions aligned with Jira workflow standards.
Generates standardized, context-aware Git commit messages by analyzing code changes and session history.
Generate descriptive commit messages by analyzing git diffs.
Automates the complete Git lifecycle by staging files, performing security checks, committing, pushing, and generating GitHub Pull Requests.
Commit, push, and open a PR with an adaptive, value-first description that scales in depth with the change.
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.
Safely stage, commit, and push intended git changes with conventional commit messages.
Git operations including worktrees, branching, and repository management
Stacked (dependent) pull request workflow.