Tweak GitHub review conditions (#36)

Author: francoischalifour

rules/communication.md

@@ -6,6 +6,7 @@
 - Do not post a comment when a heartbeat finds nothing actionable — return HEARTBEAT_OK to the invoker only; no GitHub activity.
 - Close the loop: acknowledge feedback, state what you did, mark resolved.
 - When blocked: explain what you tried, what you found, and what decision you need. Apply `needs-human-review`.
+- **Attribution**: when tagging or mentioning someone on GitHub (review requests, pings, escalations), tag the person who requested the action — not an arbitrary team member. If an instruction came from Slack, the requester is the person who sent the Slack message. If no specific requester, fall back to recent commit activity or round-robin from `USER.md`.
 - Within 5 minutes of posting, edit in place instead of adding a new comment — unless the update needs to surface as a new notification.
   - Prefer `gh pr edit --body-file` for PR descriptions.
   - Prefer `gh issue comment --edit-last --body-file` (or `gh api PATCH` with `--input`) for comments.

rules/team.md

@@ -4,6 +4,7 @@ Core team roster is in `USER.md`. All members have equal privilege.
 
 ## Reviewing PRs
 
+- **Never review your own PRs.** If you authored or co-authored a PR, skip it entirely — request a review from a team member instead.
 - **Team PRs**: Concise. Focus on correctness, edge cases, test coverage. Skip style nitpicks. Trust their architecture judgment — raise concerns, don't block.
 - **External PRs**: Welcoming. Clear, actionable feedback with examples. Offer to help if changes are close.
 

skills/routine-maintainer/SKILL.md

@@ -27,7 +27,7 @@ Dispatched by the heartbeat. Processes GitHub notifications and dispatches to `o
 ### Medium priority (this week)
 
 1. **Open issues needing triage**: Apply labels, check for duplicates
-2. **PRs awaiting review**: Review using [ops-review](../ops-review/SKILL.md) workflow
+2. **PRs awaiting review**: Review using [ops-review](../ops-review/SKILL.md) workflow (skip PRs you authored — request a team member review instead)
 3. **Issues labeled `cross-sdk-divergence`**: Check if the divergence has been resolved by a subsequent PR
 
 ### Low priority (backlog)