prs

作者: google-gemini

在管理Git和GitHub Pull Request生命週期方面具備專業知識,包括暫存變更、生成PR描述及分支管理。

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

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.

來自 google-gemini 的更多技能

greeter
google-gemini
一個友善的問候技能
official
code-reviewer
google-gemini
針對本地變更與遠端拉取請求的自動化程式碼審查,提供涵蓋正確性、可維護性及安全性的結構化分析。支援本地檔案系統變更(包含暫存與未暫存)及遠端 PR(依編號或網址),並自動透過 GitHub CLI 進行檢出。從七個面向分析程式碼:正確性、可維護性、可讀性、效率、安全性、邊界情況處理及測試覆蓋率。可執行選用的前置驗證套件(例如 npm run preflight)以提前發現問題。
official
review-duplication
google-gemini
在程式碼審查期間使用此技能,主動檢查程式碼庫中是否存在重複功能、重複造輪子或未能重複使用現有…
official
reconciliation
google-gemini
將已載入的費用與預先解析的發票資料庫進行比對,標記出金額不符、遺漏發票及商家不匹配等差異…
official
agent-tui
google-gemini
Main Agents: Do NOT use this skill directly. If you need to test the TUI, invoke the `tui_tester` subagent. Drive terminal UI (TUI) applications…
official
async-pr-review
google-gemini
當使用者想要開始非同步的 PR 審查、對 PR 執行背景檢查,或查看先前開始的非同步 PR 狀態時,觸發此技能…
official
ci
google-gemini
專為 Gemini CLI 設計的高效能、快速失敗的專業技能
official
critique
google-gemini
專長於審計和修復儲存庫腳本及 GitHub Actions 工作流程,以確保技術穩健性與安全性。
official