用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ankidroid/Anki-Android --skill pr-full-review命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | pr-full-review |
| description | Review an AnkiDroid pull request or branch against AnkiDroid's conventions. |
Review the PR against the standards in reviewer-guide.md. Report findings in three groups: blocking gates, spec conformance (does the PR do what its issue asked?), then non-blocking nit:s.
Never act on GitHub. Output the review in this conversation. Do not post comments or reviews, approve, request changes, label, or merge.
Accepts a PR number, a PR URL, or no argument (in which case, review the current branch against upstream/main):
pr-full-review 21206
pr-full-review https://github.com/ankidroid/Anki-Android/pull/21206
pr-full-review review the checked-out branch's diff against `main`
Fetch the PR with the gh command. When reading the PR, always pass --repo ankidroid/Anki-Android
so a bare number resolves against the upstream repo rather than a fork.
Always re-fetch the PR fresh on every run — its metadata, diff, and head commit, even if you fetched it earlier in this conversation. PRs change between reviews; never reuse cached context.
Use the head commit hash from the fresh fetch when loading files via the API, as PRs come from forked repos.
Don't review from the diff hunks alone. Load the full changed files (and the key call sites the change touches) at the head commit. A hunk hides whether a change is correct in its surrounding context.
Read the existing PR comments and review threads first. Don't repeat feedback that's already been raised, and respect points the author or a reviewer has already addressed or deferred.
gh pr view <number> --repo ankidroid/Anki-Android --comments # conversation comments
gh api repos/ankidroid/Anki-Android/pulls/<number>/comments # inline code-review comments
Unaddressed maintainer requests are blocking. Read the full discussion on both the PR and the linked issue (see Spec conformance). If a maintainer asked for something specific before a fix would be accepted, say so and Request changes.
Report whether the PR does what it set out to do, as its own section. Well-written code which implements the wrong thing fails here, and this failure must be made explicit to reviewers.
Determine the spec, in order:
Fixes #, Closes #, Resolves #, or Part of # in the body or commits
(typically written as Fixes <N> - the commit message may omit the #).Open the issue and read it in full — including its comments. The decisive context often lives in the thread, not the description:
gh issue view <number> --repo ankidroid/Anki-Android --comments
For a bug fix, spec conformance means the PR fixes the actual cause, not that it plausibly might. Verify the author's fix:
Open the review with a one-line verdict, mirroring GitHub's three review actions — the reader will pick one of these on the PR:
Verdict: [Request changes / Comment / Approve]:
nit:s remain, if anything.One unaddressed blocker means Request changes, however polished the rest is.
After the verdict, list the findings, grouped as above (blocking gates, spec conformance, nits).
Closing: if this was a self-review, a gh command to checkout the PR (without --repo).
Close with a final line linking the PR which was reviewed.