athene-pr-review

原文涵盖的主题

• Athene: PR Review
• 1. Which PR
• 2. Get the diff — try in this order, stop at the first that works
• 3. Check the head and base before posting
• 4. Review, scoped to the diff
• 5. Draft, show, confirm
• 6. Post — only after explicit yes, one comment, one time

Give one named, open pull request the same quality bar as Athene: Code Health, scoped to just that PR's diff, then post the result as one ordinary PR comment — only after the user confirms the exact text. Never: touch a second PR in the same run, approve, merge, request changes as a formal review state, trigger CI, or change branch/repo settings. One diff in, one comment out. Ask if not already named: repo (owner/repo) and PR number, or a PR URL containing both. Confirm it's still open before reading it — don't review a PR that's already closed or merged. 1. Public repo, no credential needed: fetch https://patch-diff.githubusercontent.com/raw/ / /pull/ .diff (or the PR's .diff URL) for the diff, and https://api.github.com/repos/ / /pulls/ (also unauthenticated, rate-limited, for public repos) for its state, head.sha, and base.ref — step 3 below needs those. Reads nothing from the user's machine. 2. A GitHub MCP server is configured: check per references/connector-detection.md in this skill. If present, use its PR-read tool instead of step 1 or 3 — it already carries whatever auth it needs, this skill never touches that credential directly. 3. Private repo and no MCP server, or step

这里只展示节选，请以完整原文和当前要求为准。