google-gemini/prs
Expertise in managing the Git and GitHub Pull Request lifecycle, including staging changes, generating PR descriptions, and branch management.
npx skills add https://github.com/google-gemini/gemini-cli --skill prs
Standardize how the Gemini CLI Bot stages its changes, generates Pull Request
descriptions, and manages the lifecycle of both new and existing PRs.
If you are proposing fixes and PR creation is enabled (per the System Directive):
changes. Changes are unrelated if they address different root causes.
unrelated refactor, or a metrics script update. Metrics and fixes MUST
be in separate PRs.
write_file tool to createpr-description.md.
it is recommended, and the expected impact.
git add <files> command.
staging internal bot management files. If they are accidentally staged, you
MUST unstage them using git reset <file>.
pr-description.md, lessons-learned.md,branch-name.txt, pr-comment.md, pr-number.txt, issue-comment.md, or
anything in history/.
If you are continuing work on an existing Task or responding to a comment on an
existing bot PR:
write_file to generate branch-name.txtcontaining the current branch name (e.g., bot/task-BT-01).
write_file to generate pr-number.txt containing thenumeric PR ID.
issue-comment.md.pr-comment.md.gh run view. Yourpriority must be generating a new patch and staging it with git add to fix
the failure.
Take google-gemini/prs from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.