From 3c7203f79e603b5ee62d4ee02351b94d17f7ed44 Mon Sep 17 00:00:00 2001
From: Coco Sheng <cocosheng@google.com>
Date: Wed, 8 Apr 2026 16:06:17 -0400
Subject: [PATCH] docs(skills): add key model and diff/edit functionalities to
 maintainer-only criteria

---
 .../builtin/github-issue-triage/references/triage_rules.md   | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/packages/core/src/skills/builtin/github-issue-triage/references/triage_rules.md b/packages/core/src/skills/builtin/github-issue-triage/references/triage_rules.md
index f537ca8ec3..0c6d79acfd 100644
--- a/packages/core/src/skills/builtin/github-issue-triage/references/triage_rules.md
+++ b/packages/core/src/skills/builtin/github-issue-triage/references/triage_rules.md
@@ -115,8 +115,11 @@ Search for duplicates using `gh issue list --search "<keywords>" --repo <owner/r
 ## Step 6: Triage Summary
 Review the issue comments to see if a community member has already identified the root cause.
 - If a root cause is identified: determine if it is a very simple fix. If it is a simple fix, post guidance for the fix, categorize the issue as **Maintainer-only**, and explain why. If it is not a simple fix, determine whether it should be **Maintainer-only** or **Help-wanted** and explain why. 
-- If no root cause is identified: State whether the issue should be categorized as **Maintainer-only** (epic, core architecture, sensitive fixes, internal tasks, issues requiring deep investigation, changes to key UI/UX that affect all users, modifications to core internal data structures and IPC mechanisms, or changes to token/billing logic and key model functionalities) or **Help-wanted** (small well-defined features, easy-to-fix bugs, good for community, or tasks ready for external help). Your comment should be brief and clearly explain *why* it fits that category. 
+- If no root cause is identified: State whether the issue should be categorized as **Maintainer-only** (epic, core architecture, sensitive fixes, internal tasks, issues requiring deep investigation, changes to key UI/UX that affect all users, modifications to core internal data structures and IPC mechanisms, changes to token/billing logic, or changes to key model and diff/edit functionalities) or **Help-wanted** (small well-defined features, easy-to-fix bugs, good for community, or tasks ready for external help). Your comment should be brief and clearly explain *why* it fits that category. 
 - If you categorized the issue as **Help-wanted**, also run `gh issue edit <issue_url> --remove-label "status/need-triage" --add-label "help wanted"`. 
 - If you categorized the issue as **Maintainer-only**, also run `gh issue edit <issue_url> --remove-label "status/need-triage" --add-label "🔒 maintainer only"`.
 - Action: `gh issue comment <issue_url> --body "### Triage Summary\n\n<your summary>"`
 - **STOP EXECUTION**.
+`
+- **STOP EXECUTION**.
+ION**.