MediaMetz/gemini-cli
1
0
Fork 0
mirror of https://github.com/google-gemini/gemini-cli.git synced 2026-07-04 23:27:00 -07:00
Code Issues Packages Projects Releases Wiki Activity

docs(bot): clarify PR maintenance expectations in prs skill

Browse Source
This commit is contained in:
Christian Gunderman
2026-05-14 20:12:34 -07:00
parent 6b7174703c
commit 295c0ac072
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tools/gemini-cli-bot/.gemini/skills/prs/SKILL.md
+6 -1
View File
@@ -15,7 +15,12 @@ descriptions, and manages the lifecycle of both new and existing PRs.
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.
2. **Resolution Priority**:
- **Fixable CI/Feedback**: If a `bot-fix` PR has failing status checks or new maintainer comments, you MUST prioritize fixing the CI or responding to the feedback before starting new work.
- **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.
2. **Test Failures**: Fix any failing unit or integration tests related to the PR.
3. **Failing Checks**: Resolve any failing status checks (e.g., lint, build, typecheck).
4. **PR Comments**: Address and resolve all maintainer comments and requested changes.
You MUST prioritize this maintenance before starting new work.
- **Unresolvable Roadblocks**: If you identify a persistent failure that appears to be an environment issue, a flaky test, or a fundamental architectural blocker that requires human intervention, you MUST NOT keep looping. Instead:
1. Summarize the blocker and your failed attempts in `pr-comment.md`.
2. Explicitly ask for maintainer help.