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 6d854b91a8..d6bf64ebe1 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
@@ -30,7 +30,8 @@ If there is a cross-referenced PR in `cross_references` where `is_pr` is `true`
   c. If **Maintainer-only**, run `gh issue edit <issue_url> --remove-label "status/need-triage" --add-label "🔒 maintainer only"`.
   d. If **Help-wanted**, run `gh issue edit <issue_url> --remove-label "status/need-triage" --add-label "help wanted"`.
   e. Execute `gh issue comment <issue_url> --body "### Triage Summary\n\nWhile this issue is valid, the proposed fix in PR <pr_url> introduces potential breaking changes or relies on incorrect assumptions (e.g., <brief explanation of the flaw>). Therefore, we will not reopen that PR, but we still welcome a different approach to fix this issue!"`
-  f. **STOP EXECUTION**.
+  f. Comment on the PR: `gh pr comment <pr_url> --body "@<author_username>, thank you for your contribution! We've reviewed the approach in this PR and decided to keep it closed because <brief explanation of the flaw>. We still welcome improvements here using a different approach! Feel free to open a new PR if you're interested."`
+  g. **STOP EXECUTION**.
 - If it is worth resuming AND was closed by a bot:
   a. Determine if the issue should be **Maintainer-only** (epic, core architecture, sensitive fixes, internal tasks, issues requiring deep investigation, changes to key UI/UX that affect all users, or modifications to core internal data structures and IPC mechanisms) or **Help-wanted** (small well-defined features, easy-to-fix bugs, good for community, or tasks ready for external help).
   b. If it should be **Maintainer-only**: