prs

作成者: google-gemini

Expertise in managing the Git and GitHub Pull Request lifecycle, including staging changes, generating PR descriptions, and branch management.

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(番号またはURL指定)の両方をサポートし、GitHub CLIによる自動チェックアウトを実行。コードを正確性、保守性、可読性、効率性、セキュリティ、エッジケース処理、テストカバレッジの7つの観点で分析。オプションで事前検証スイート(例: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