
GitHub PR & Git Management
OfficialFreeStreamline your Git and GitHub Pull Request processes.
Free · Opens the source repo
What GitHub PR & Git Management does
The GitHub PR & Git Management skill is designed to enhance the workflow of developers by standardizing the management of Pull Requests (PRs) within the Gemini CLI Bot. This skill emphasizes best practices in staging changes, generating PR descriptions, and handling the lifecycle of both new and existing PRs. By following the outlined procedures, developers can ensure that their contributions are well-organized and clearly communicated.
One of the key features of this skill is the strict guideline against bundling unrelated changes in a single PR. This means that each PR should focus on a single improvement or fix, which helps maintain clarity and makes it easier for maintainers to review changes. The skill also automates the generation of PR descriptions, requiring developers to provide a concise title and a detailed explanation of the changes made, their rationale, and the expected impact. This structured approach not only aids in documentation but also improves collaboration by making the intent behind changes clear.
In addition to managing new PRs, this skill provides guidance for updating existing PRs. Developers are instructed to track their current branch and PR ID, ensuring that any updates or responses to maintainers are accurately documented. The skill also includes protocols for addressing Continuous Integration (CI) failures, emphasizing the importance of diagnosing issues and staging necessary fixes promptly. This focus on recovery and responsiveness helps maintain the momentum of development work.
Overall, the GitHub PR & Git Management skill is ideal for developers looking to improve their Git and GitHub workflows. By adhering to the outlined practices, they can enhance the quality of their contributions and facilitate smoother collaboration within teams.
When to use it
Use this skill when you need to manage PRs effectively within the Gemini CLI Bot, ensuring compliance with best practices.
When not to use it
This skill may not be suitable for projects that require more flexible PR management or for teams that do not follow strict Git workflows.
What you can build with it
Creating a New Pull Request
When proposing a fix, use this skill to ensure you create a well-structured PR that adheres to best practices.
Updating an Existing PR
If you need to respond to feedback on an existing PR, this skill guides you in tracking your branch and PR ID effectively.
Handling CI Issues
Use this skill to diagnose and resolve CI failures, ensuring your changes are staged and ready for review.
How to install GitHub PR & Git Management
View source1. Install with the skills CLI
npx skills add google-gemini/gemini-cli/prs --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by google-geminiSkill: 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_filetool to createpr-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 inhistory/.
- NEVER STAGE:
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_fileto generatebranch-name.txtcontaining the current branch name (e.g.,bot/task-BT-01). - Track PR ID: Use
write_fileto generatepr-number.txtcontaining 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.
- For general responses, write your markdown comment to
- Handle CI Failures: Diagnose failing checks using
gh run view. Your priority must be generating a new patch and staging it withgit addto fix the failure.
Frequently asked questions about GitHub PR & Git Management
Similar skills
Release Candidate Preparation
Streamline your OpenAI Agents release process.
Gitmoji
Generate expressive commit messages with emojis.
GitHub Release
Automate your GitHub library release process effortlessly.
Commit Message Storyteller
Generate meaningful commit messages from your git diffs.
Author Contributions
Trace author contributions across branches in Git.
Implementation Kickoff
Streamline your code implementation process with ease.
