update workflow - auto assign yourself as assignee/reviewer

.codex/skills/review-pr/SKILL.md

@@ -22,11 +22,13 @@ description: Phase 2 skill. Use when a PR is created or updated. Review PR again
 
 1. **Load PR and issue**
    - Read PR: `mcp__gitea__.pull_request_read` (`method: "get"`).
+   - If PR is already merged or closed, say so and stop.
+   - Read current Gitea user: `mcp__gitea__.get_me`.
+   - Read existing reviews: `mcp__gitea__.pull_request_read` (`method: "get_reviews"`).
+   - If the current user is not already requested as a reviewer and has not already reviewed this PR, add them with `mcp__gitea__.pull_request_write` (`method: "add_reviewers"`).
    - Identify the linked issue from PR body (`Fixes #<id>` or `Closes #<id>`).
    - Read issue comments, find the **Final Requirements** comment: `mcp__gitea__.issue_read` (`method: "get_comments"`).
-   - Read existing reviews: `mcp__gitea__.pull_request_read` (`method: "get_reviews"`).
    - Read PR discussion comments: `mcp__gitea__.issue_read` (`method: "get_comments"`), using the PR number as the index.
-   - If PR is already merged or closed, say so and stop.
 
 2. **Read review history** (for re-reviews)
    - Get review comments: `mcp__gitea__.pull_request_read` (`method: "get_review_comments"`).
@@ -101,6 +103,7 @@ Validation:
 
 ## Rules
 - Use Gitea MCP tools for all PR/review operations.
+- Do not add yourself as reviewer twice; check requested reviewers and existing reviews first.
 - Do NOT edit code on the PR.
 - FAIL if PR contains unrelated changes or scope creep.
 - Post review proactively if verdict is clear.