google-gemini/gemini-cli125 installs

prs

Q: How do I install this agent skill?

Run npx skills add https://github.com/google-gemini/gemini-cli --skill prs.

Q: Is this agent skill safe to install?

Review the displayed partner audits, complete source, permissions, dependencies, and exact revision before installing.

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

How do I install this agent skill?

npx skills add https://github.com/google-gemini/gemini-cli --skill prs

view source ↗

Is this agent skill safe to install?

Gen Agent Trust Hubpass
This skill provides a standard workflow for managing Git and GitHub Pull Requests. It includes security considerations regarding the ingestion of external data from GitHub, which is a common pattern for automated PR management. These elements are used within the skill's intended functionality to help maintain standard Git practices.
Socketpass
No alerts
Snykwarn
Risk: MEDIUM · 1 issue

What does this agent skill do?

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 can the creator link this skill?

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/google-gemini/gemini-cli/prs">View prs on skillZs</a>