0xa3b/git

Drive automated-review feedback on an existing GitHub pull request to current-head approval or a clearly reported exception. Use when the user asks to handle, address, or drive bot or automated review feedback on a pull request through review rounds to approval, wait for or poll a review bot, disposition and resolve its review threads, or request a follow-up automated review after pushing fixes. Do not use for reviewing the session's own changes locally, human-only review comments, CI repair, creating or refreshing a pull request, merging, or triaging findings delivered outside a pull request's automated review, such as sub-agent or in-session review-agent findings.

Creates git commits using Conventional Commit messages after reviewing current changes and splitting logical units. Use when the user asks to commit current work, create commits, batch commits, commit only a selected scope or subset of the changes, or run a fast commit workflow. Also use when no repository commit convention is specified. Do not use for message-only drafting, syntax validation, split guidance without commit execution, conceptual commit questions, history inspection, user prompts or loaded repository instructions that reject Conventional Commits or request Gitmoji or another commit-message standard, or ordinary-language uses of "commit" such as committing to a plan.

Prepare and create or refresh a GitHub pull request or GitLab merge request from the current branch. Use when the user asks to create, open, or publish the current branch's pull request or merge request, or to refresh an existing change request after current-branch changes, including operational branch preparation, validation, normal push, authored title and description, and initial CI observation. Do not use for metadata-only change-request edits, drafting a description without publishing, code review, review-feedback handling, merging, or conflict resolution.

Merge a ready GitHub pull request or GitLab merge request and verify remote and local cleanup. Use when the user asks to merge or land a specific pull request or merge request, including checking forge merge gates, selecting the merge method, observing the merge, deleting branches, and refreshing ignored SHA references. Do not use for merging one branch into another locally, resolving merge conflicts, squashing or rewriting local history, merging code such as functions or files, creating change requests, handling review feedback, or bypassing protections.