prs

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Automated bots and agents often create messy pull requests by bundling unrelated changes, forgetting to stage files, or accidentally committing internal management files. This Skill standardizes how an agent stages changes, writes PR descriptions, and maintains existing PRs. ## Core Features & Use Cases - Surgical Change Enforcement: Restricts each PR to a single improvement or fix, forbidding the bundling of unrelated changes such as mixing script fixes with documentation updates. - PR Description Generation: Creates a pr-description.md file with a conventional title on the first line and a markdown body explaining the change and its impact. - Internal File Protection: Prevents staging of bot management files like pr-description.md, branch-name.txt, pr-number.txt, and anything in history/. - PR Recovery & Updates: Handles existing PRs by tracking branch names and PR IDs, writing maintainer responses to issue-comment.md or pr-comment.md, and diagnosing CI failures with gh run view. - Use Case: An autonomous bot fixing a bug generates a focused patch, stages only the relevant source files, writes a conventional PR description, and responds to reviewer feedback on the same branch without polluting the commit history. ## Quick Start Stage my fix, generate a PR description, and prepare a pull request containing only this single change.

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?

Stage only the files related to one fix using git add, then write a pr-description.md file with a conventional title on the first line and a markdown body explaining the change. Never bundle unrelated changes such as mixing a script fix with documentation updates.

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

Write the current branch name to branch-name.txt and the numeric PR ID to pr-number.txt to target the existing PR. Then stage your new patch with git add and write reviewer responses to pr-comment.md or issue-comment.md.

How do I diagnose failing CI checks on a GitHub PR?

Use the gh run view command to inspect failing check logs and identify the root cause. Then generate a new patch addressing the failure and stage it with git add so the PR checks can rerun.

Why should bot management files be excluded from git staging?

Internal files like pr-description.md, branch-name.txt, and pr-number.txt are workflow artifacts, not product changes. Committing them pollutes the repository history, so they must be unstaged with git reset if accidentally added.

What are the limitations of automated PR creation workflows?

Automated PR workflows require explicit staging discipline and cannot judge whether two changes share a root cause without clear rules. They also depend on PR creation being enabled by the governing system directive before proposing fixes.