Prs

Name: Prs
Author: google-gemini

google-gemini/gemini-cli

96 installs
106k repo stars
Updated August 5, 2026
google-gemini/gemini-cli

How does the Gemini CLI Bot standardize its Git workflow, enforce single-fix PRs, generate PR descriptions, and recover from CI failures?

About

The GitHub PR & Git Management skill standardizes how the Gemini CLI Bot handles the entire pull request lifecycle. It enforces surgical, single-fix changes per PR, auto-generates standardized PR descriptions, and manages branch/PR metadata files. The skill includes staged file management with strict internal file protection, recovery workflows for existing PRs, and CI failure diagnosis. Developers integrate this when automating code contributions, ensuring conventional commit practices, preventing bundled unrelated changes, and maintaining clean audit trails. Critical guards prevent accidental staging of bot management files like pr-description.md and lessons-learned.md.

Single-fix-per-PR enforcement prevents bundled unrelated changes
Auto-generates PR descriptions with conventional commit titles and markdown bodies
Surgical staging with git add combined with internal file protection guards
Recovery workflows for existing PRs with branch-name.txt and pr-number.txt tracking
CI failure diagnosis and patch regeneration via gh run view integration

Prs by the numbers

96 all-time installs (skills.sh)
Ranked #231 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
Data as of Aug 5, 2026 (Skillselion catalog sync)

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

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/google-gemini/gemini-cli/prs.svg)](https://skillselion.com/skills/google-gemini/gemini-cli/prs)

Installs	96
repo stars	★ 106k
Last updated	August 5, 2026
Repository	google-gemini/gemini-cli ↗

What it does

Automate PR lifecycle management, staging, description generation, and CI failure recovery for bot-driven contributions.

Who is it for?

Bot-driven code contribution workflows, automated refactoring agents, CI-integrated development tools, multi-PR orchestration systems.

Skip if: Manual pull request creation, single-commit workflows, non-agent git management, systems without GitHub API access.

When should I use this skill?

Proposing code fixes or improvements via PR, responding to maintainer feedback, diagnosing and fixing CI failures, managing multiple bot PRs in parallel.

What you get

Developers and bot maintainers achieve surgical, traceable, conventional-commit-compliant PRs with clear descriptions, protected metadata, and automated CI recovery.

Files

SKILL.mdMarkdownGitHub ↗

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):

1. 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. 2. 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. 3. Stage Fixes: You MUST explicitly stage your fixes using the git add <files> command. 4. 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:

1. Target Existing Branch: Use write_file to generate branch-name.txt containing the current branch name (e.g., bot/task-BT-01). 2. Track PR ID: Use write_file to generate pr-number.txt containing the numeric PR ID. 3. 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.

4. 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.