Github Pr

GitHub Workflow

This skill guides the process of moving local changes to a GitHub Pull Request.

Prerequisites

• git must be installed and configured.
• gh (GitHub CLI) must be installed and authenticated.

Commit Message Format

Use Conventional Commits with this required format: ():

• type REQUIRED. Common values: feat, fix, docs, refactor, chore,

test, perf, ci, build, style.

• scope REQUIRED. Short noun for the changed area (for example: config,

api, ui, docs).

• summary REQUIRED. Imperative, /`.
• Execute when a new branch is needed: git checkout -b

1. Review & Stage Changes

• Review changes with git status and git diff.
• By default, stage only the files that belong to the current requested change.
• If the user provided file paths/globs, stage only those files.
• If there are ambiguous extra changed files, ask before staging/committing and leave them unstaged unless the user explicitly includes them.
• Stage the intended files with git add ....
• Optionally inspect recent subjects for local scope patterns:

git log -n 10 --pretty=format:%s.

1. Commit

• Propose a message in exact format:

(): .

• Execute: git commit -m ""
• If pre-commit hooks fail, diagnose and fix the issues before re-staging and re-committing.
• Do not move on to PR actions until the commit succeeds.

1. Push

• Push the committed branch to the remote before any PR creation or review trigger.
• If this is the first push for the branch, use: git push -u origin
• If the upstream is already set, use: git push
• Never post /gemini review before the push succeeds for the latest commit.

1. Pull Request Handling

• Only after a successful push, check whether a PR for the current branch already exists.
• Use gh pr view --json url,number,headRefName to detect an existing PR for the checked-out branch.
• If no PR exists:
• Create the PR using gh pr create.
• Provide a concise title (often the commit message) and a body summarizing the changes.
• Execute: gh pr create --title "" --body ""
• Share the generated PR URL with the user.
• If a PR already exists:
• Do not open a duplicate PR.
• After the push succeeds, add a PR comment containing exactly /gemini review to trigger the code quality review.
• Execute: gh pr comment --body "/gemini review"
• Share the existing PR URL with the user and mention that the review trigger comment was added after pushing the new commit.

Common Failures

• Pre-commit hooks: If hooks fail, fix the files and stage them again before committing.
• Untracked files: Ensure new files are added.
• Remote branch already exists: If the branch exists, ask the user if they want to overwrite or use a different name.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: mfmezger
• Source: mfmezger/aiagent_dotfiles
• License: MIT

Install and usage instructions live in the source repository linked above.