mcpbeat

Prs

google-gemini/prs

Expertise in managing the Git and GitHub Pull Request lifecycle, including staging changes, generating PR descriptions, and branch management.

610 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
106350
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/google-gemini/gemini-cli --skill prs

The instruction itself

4 sections, as written by the author

Skill: GitHub PR & Git Management

Goal

Standardize how the Gemini CLI Bot stages its changes, generates Pull Request

descriptions, and manages the lifecycle of both new and existing PRs.

Staging & Patch Preparation (MANDATORY)

If you are proposing fixes and PR creation is enabled (per the System Directive):

  • Surgical Changes: Only propose a single improvement or fix per PR.
  • No Bundling: You are STRICTLY FORBIDDEN from bundling unrelated

changes. Changes are unrelated if they address different root causes.

  • Examples: Do not combine a script fix with a documentation update, an

unrelated refactor, or a metrics script update. Metrics and fixes MUST

be in separate PRs.

  • Generate PR Description: Use the write_file tool to create

pr-description.md.

  • Title: The very first line MUST be a concise, conventional title.
  • Body: The rest should be the markdown body explaining the change, why

it is recommended, and the expected impact.

  • Stage Fixes: You MUST explicitly stage your fixes using the

git add <files> command.

  • Internal File Protection (CRITICAL): You are STRICTLY FORBIDDEN from

staging internal bot management files. If they are accidentally staged, you

MUST unstage them using git reset <file>.

  • NEVER STAGE: pr-description.md, lessons-learned.md,

branch-name.txt, pr-comment.md, pr-number.txt, issue-comment.md, or

anything in history/.

Unblocking & PR Updates (Recovery)

If you are continuing work on an existing Task or responding to a comment on an

existing bot PR:

  • Target Existing Branch: Use write_file to generate branch-name.txt

containing the current branch name (e.g., bot/task-BT-01).

  • Track PR ID: Use write_file to generate pr-number.txt containing the

numeric PR ID.

  • Respond to Maintainers:
  • For general responses, write your markdown comment to issue-comment.md.
  • For specific PR feedback, write your markdown response to pr-comment.md.
  • Handle CI Failures: Diagnose failing checks using gh run view. Your

priority must be generating a new patch and staging it with git add to fix

the failure.

How to use it

Copy the folder

Take google-gemini/prs from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.