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 的更多技能

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…
gemini-api-cli
google-gemini
使用 Gemini API CLI 工具的指南。當你需要透過命令列與 Gemini API 互動、管理代理或生成媒體(圖片、……)時使用。
behavioral-evals
google-gemini
建立、執行、修正及推廣行為評估的指引。用於驗證代理決策邏輯、除錯失敗、除錯提示…
gemini-live-api-dev
google-gemini
通過WebSocket與Gemini進行即時雙向串流,支援音訊、視訊和文字對話。支援音訊輸入/輸出(16 kHz PCM)、視訊幀、文字,以及具備語音活動偵測的自動轉錄功能,可處理中斷情況。包含原生音訊功能:情感對話、主動音訊和思考模式;支援同步和非同步工具使用的函式呼叫;以及Google Search基礎驗證。提供具備上下文壓縮、恢復功能的會話管理,以及...
gemini-omni-flash-api
google-gemini
使用此技能進行生成式影片編輯、文字轉影片、圖片參考影片生成,以及基於…的首幀轉場動畫。
gemini-api-dev
google-gemini
We need to translate the given text from English to Traditional Chinese. The text describes building applications with Google's Gemini models, mentioning multimodal content, function calling, structured outputs, supported languages, model versions, features, and SDKs. We must preserve the name "gemini-api-dev" but it's not in the text, so ignore. Also preserve technical terms like "Gemini", "Pro", "Flash", "Pro Image", "1M token context", "Gemini 2.x", "1.5", "JSON", "SDKs", "google-genai", etc. No extra commentary. Output only the translation. Translation: 使用 Google 的 Gemini 模型建置應用程式,支援多模態內容、函式呼叫與結構化輸出,涵蓋 Python、JavaScript、Go 及 Java。可存取最新的 Gemini 3 模型(Pro、Flash、Pro Image),具備 100 萬 Token 上下文;舊版 Gemini 2.x 與 1.5 模型已棄用。支援文字生成、圖片/音訊
gemini-interactions-api
google-gemini
Gemini模型與代理的統一介面,具備伺服器端狀態、串流與工具編排功能。支援多種當前模型(gemini-3-flash-preview、gemini-3-pro-preview、gemini-2.5-flash/pro)及Deep Research代理;自動將已棄用的模型ID替換為當前替代方案。透過previous_interaction_id將對話歷史卸載至伺服器,實現有狀態的多輪互動,無需手動管理歷史記錄。內建工具編排功能,包括...
deliver
google-gemini
將簡報的精簡版本發布到 Google Chat 或 Slack 的 incoming webhook,讓每日執行自動送達——若未設定 webhook 則靜默跳過…