prs

Manages Git staging and GitHub pull request lifecycle for automated bot workflows.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/bkrsna/gemini-cli --skill prs-bkrsna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prs
Source: https://github.com/bkrsna/gemini-cli/tree/main/tools/gemini-cli-bot/.gemini/skills/prs
Command: npx skills add https://github.com/bkrsna/gemini-cli --skill prs-bkrsna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Automated bots often create messy pull requests by bundling unrelated changes, staging internal management files, or losing track of existing PR branches. This Skill standardizes how an AI agent stages changes, writes PR descriptions, and continues work on existing PRs. ## Core Features & Use Cases - Surgical Change Staging: Enforces one fix per PR and explicitly stages only relevant files with git add, while forbidding internal bot files like pr-description.md or branch-name.txt from being committed. - PR Description Generation: Creates pr-description.md with a conventional title on the first line and a markdown body explaining the change and its impact. - Existing PR Recovery: Tracks branch names and PR IDs via branch-name.txt and pr-number.txt, writes maintainer responses to issue-comment.md or pr-comment.md, and diagnoses CI failures with gh run view. - Use Case: A bot fixing a failing CI check on its own PR can regenerate the patch, stage only the fix, and reply to reviewer feedback without polluting the commit with internal state files. ## Quick Start Use the prs skill to stage my fix, generate a PR description, and update the existing pull request with a response to the reviewer comment.

Frequently Asked Questions about prs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a pull request with a single focused change using git?

Stage only the files related to one fix using git add, then write a PR description with a conventional title on the first line followed by a markdown body explaining the change and its impact. Never bundle unrelated fixes into the same PR.

How to update an existing GitHub pull request from a bot?

Record the current branch name in branch-name.txt and the numeric PR ID in pr-number.txt so the bot targets the existing PR. Write reviewer responses to pr-comment.md or general replies to issue-comment.md, then stage and push the new patch.

How do I diagnose failing CI checks on a GitHub pull request?

Use the gh run view command to inspect failing check logs and identify the root cause. Then generate a corrected patch, stage it with git add, and push it to the existing PR branch.

Why should internal bot files be excluded from git staging?

Files like pr-description.md, branch-name.txt, and pr-number.txt are operational state for the bot, not part of the codebase. Committing them pollutes the repository history, so they must be unstaged with git reset if accidentally added.

What are the limitations of automated PR management for bots?

The workflow assumes PR creation is enabled by the system directive and relies on file-based state tracking rather than a database. It handles one fix per PR and requires manual policy enforcement to prevent bundling unrelated changes.