From 7fb9e05d3636b3b732982941993094eb9e6d61c7 Mon Sep 17 00:00:00 2001 From: Christian Gunderman Date: Fri, 15 May 2026 09:16:06 -0700 Subject: [PATCH] docs(bot): use robust search and explicit repo in prs skill --- tools/gemini-cli-bot/.gemini/skills/prs/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/gemini-cli-bot/.gemini/skills/prs/SKILL.md b/tools/gemini-cli-bot/.gemini/skills/prs/SKILL.md index 5d6937ae63..cebae992a5 100644 --- a/tools/gemini-cli-bot/.gemini/skills/prs/SKILL.md +++ b/tools/gemini-cli-bot/.gemini/skills/prs/SKILL.md @@ -13,7 +13,7 @@ descriptions, and manages the lifecycle of both new and existing PRs. ## Mandatory PR Driver (Ownership) You are the "owner" of all PRs labeled `bot-fix`. You MUST proactively drive them toward a resolution (either completion or informed escalation): -1. **Inventory**: Use `gh pr list --label "bot-fix" --json number,title,headRefName,statusCheckRollup,comments` to find your active PRs. +1. **Inventory**: Use `gh pr list --search "is:open is:pr label:bot-fix" --repo google-gemini/gemini-cli --json number,title,headRefName,statusCheckRollup,comments` to find your active PRs. 2. **Resolution Priority**: - **Fixable CI/Feedback**: If a `bot-fix` PR needs attention, you MUST prioritize driving it to completion by resolving issues. Specifically: 1. **Merge Conflicts**: Attempt to resolve merge conflicts by pulling the target branch or rebasing.