From ddf042cae6be7cfab4efd0151b408753ac281179 Mon Sep 17 00:00:00 2001 From: Keith Guerin Date: Thu, 26 Mar 2026 14:14:43 -0700 Subject: [PATCH] docs(ux): formalize Google Chat review request protocol --- .../gemini-cli-ux/skills/ux-git-workflow/SKILL.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/packages/extensions/gemini-cli-ux/skills/ux-git-workflow/SKILL.md b/packages/extensions/gemini-cli-ux/skills/ux-git-workflow/SKILL.md index 815ea04788..cdcfd12636 100644 --- a/packages/extensions/gemini-cli-ux/skills/ux-git-workflow/SKILL.md +++ b/packages/extensions/gemini-cli-ux/skills/ux-git-workflow/SKILL.md @@ -128,6 +128,13 @@ If operating in a sibling worktree (e.g., `feature-xyz/`): 2. If checks fail, fetch the failure logs, diagnose the issue, apply a fix, push the update, and loop back to step 1. 3. Once you verify that ALL checks have passed, you must ask the user if they want to mark the PR as ready for review (or remind them to do so themselves). Do not mark it ready without explicit user verification. +#### 11. Requesting Review (Google Chat) +- **Context**: The engineering manager requests that all PRs passing checks and ready for review be posted to a specific Google Chat space so reviewers can pick them up. +- **Action**: After the PR is marked ready for review: + 1. Prepare a draft message summarizing the PR (e.g., "Hi team, PR # is ready for review: - <Link>"). + 2. Present the draft message to the user along with a direct link to the chat space: [Gemini CLI PR Review Requests](https://chat.google.com/room/AAQAKYbF9sM?cls=7). + 3. If the user has the Google Workspace CLI (`gws`) or relevant MCP installed, proactively offer to post the message to the space on their behalf. + **Note**: If any step fails, do NOT claim completion. Fix the issue and restart from Step 1. ---