prs 精选
Expertise in managing the Git and GitHub Pull Request lifecycle, including staging changes, generating PR descriptions, and branch management.
安装方式
cp -r tools/gemini-cli-bot/.gemini/skills/prs ~/.claude/skills/prs把该 skill 目录放进客户端 skills 目录。不同客户端的目录可能不同,Claude Code 默认是 ~/.claude/skills/
https://raw.githubusercontent.com/google-gemini/gemini-cli/9b6e0265d16bbd29ca51e33c9e0c01dc4cec5e83/tools/gemini-cli-bot/.gemini/skills/prs/SKILL.md下载后另存为 ~/.claude/skills/prs/SKILL.md。链接锁定采集时的 commit,内容与本站展示一致。
整仓一次性获取:git clone --depth 1 https://github.com/google-gemini/gemini-cli.git
依赖与权限
- 无需 API Key
- 无需联网
- 依赖外部命令:
gitgh - 以上为按正文与 frontmatter 自动推断的信号,仅供参考;安装前建议先阅读原文。
SKILL.md 正文
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_filetool 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_fileto generatebranch-name.txt
containing 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.
- 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.
质量与来源
- 所属仓库
- google-gemini/gemini-cli
- 仓库星标
- 11 万
- 最近更新
- 今天
- 采集时间
- 今天
- commit
- 9b6e0265d16b
- 内容指纹
- sha256:dace221f16d4fd6
- 文件路径
- tools/gemini-cli-bot/.gemini/skills/prs/SKILL.md