From e542b8167037881a1dbd362fab7741dddbe20990 Mon Sep 17 00:00:00 2001
From: Coco Sheng <cocosheng@google.com>
Date: Thu, 9 Apr 2026 14:21:35 -0400
Subject: [PATCH] docs(triage): explicitly require triage summary for
 non-help-wanted issues in closed PR re-evaluation

---
 .gemini/skills/github-issue-triage/references/triage_rules.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.gemini/skills/github-issue-triage/references/triage_rules.md b/.gemini/skills/github-issue-triage/references/triage_rules.md
index a019074001..41e1ce48b4 100644
--- a/.gemini/skills/github-issue-triage/references/triage_rules.md
+++ b/.gemini/skills/github-issue-triage/references/triage_rules.md
@@ -71,6 +71,7 @@ If there is a cross-referenced PR in `cross_references` where `is_pr` is `true`
   a. Determine if the issue should be **Help-wanted** (using the Categorization Guide).
   b. If it should NOT be **Help-wanted**:
      - Execute `gh issue edit <issue_url> --remove-label "status/need-triage"`
+     - Execute `gh issue comment <issue_url> --body "$(echo -e "### Triage Summary\n\n<brief explanation of why this issue requires maintainer attention and is not suitable for community contribution>")"`
      - **STOP EXECUTION**. (Do not reopen the PR).
   c. If it should be **Help-wanted**:
      - Reopen the PR: `gh pr reopen <pr_url>`