review-pr SKILL.md skillA
review-pr from hsuanyulee/polaris is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add hsuanyulee/polaris/review-pr@v2.1.0Pins v2.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- hsuanyulee/polaris
- Path
.claude/skills/review-pr/SKILL.md- Versions recorded
- 6
- Latest version
- v2.1.0, committed Sep 21, 2026
- First version recorded
- Aug 24, 2026
- Size
- 8,067 bytes
- Repository stars
- 5
- License
- MIT
Review someone else's PR as a code reviewer: read the PR diff, check against .claude/rules, leave inline comments on issues found, and submit a review with APPROVE or COMMENT (REQUEST_CHANGES only when the user says so). Use when the user asks the assistant to review a PR (subject omitted or = self), e.g.: "review PR", "review 這個 PR", "review 此 PR", "review 該 PR", "幫我 review 這個 PR" (without team subject), "review for me", "code review", or shares a PR URL with self-directed review intent. NOT…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# review-pr 以 reviewer 角色審查別人的單一 PR，依 repo rules / handbook / diff context 留 inline comments，並送出 GitHub review。 ## Contract 此 skill 只處理單一 PR review。多 PR discovery 與 batch orchestration 交給 `review-inbox`；修自己的 PR review comments 就直接修（那不需要重簽成功的定義）。 Reviewer stance：prioritize bugs、behavior regressions、security、type safety、project rule violations、missing tests。不要用 personal style preference 擋 merge。 reviewer-side 屬 read-only lane，但對 `changes_requested`、`active unresolved comments`、 `awaiting_re_review`、`mergeable_ready` 的語義必須與 author-side mutable lane 一致；不得自行重寫。 本 skill 可輸出 reviewer 結論（預設是 `APPROVE` 或 `COMMENT`；`REQUEST_CHANGES` 只在使用者 明說要擋那一顆的時候，見 `references/review-pr-submit-flow.md`〈Review Action〉），但不得把 reviewer 結論寫成 author-side stage authority；「可 merge / 可 release / 已完成」仍必須沿用 shared PR / workflow state，而不是 reviewer prose。 ## 這支 skill 有沒有被叫對：`evals/evals.json` 上面那條界線（什麼走這支、什麼走 `review-inbox` / `request-pr-review`）不是只寫在散文裡， 它有一份**具名的案例集**：`evals/evals.json`，13 句真的會被打出來的話，7 句該觸發、6 句 不該。每一條帶著它為什麼在那裡（`notes`）。 **它是給人讀的，不是給腳本跑的**——這裡沒有 runner，也刻意不要有一支。它的用途是：改 frontmatter 的 `description` 之前先讀那 13 句，問「改完之後這 13 句的答案還一樣嗎」。負向 那 6 句尤其重要，因為觸發詞放寬的代價從來不出現在正向案例上。 …
Read the whole file at its exact version.
How to install
mdr add hsuanyulee/polaris/review-pr@sha256:151030ff04952f25The line at the top of this page pins the label v2.1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_3ojqvotrd4jaszeg)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Aug 24, 2026 and Sep 21, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v2.1.0 latest | 2026-09-21 | 99480f2 | 8,067 B | A | view · diff |
| v2.1.0 | 2026-09-06 | d8d271e | 7,696 B | A | view · diff |
| v2.1.0 | 2026-09-04 | 0500cde | 6,885 B | A | view · diff |
| v2.1.0 | 2026-08-29 | 4754d29 | 6,834 B | A | view · diff |
| v2.1.0 | 2026-08-28 | a2bd2a4 | 6,834 B | A | view · diff |
| v2.1.0 | 2026-08-24 | e610d9d | 6,822 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8067 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
hsuanyulee/polaris · 5 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3ojqvotrd4jaszeg GET https://markdownregistry.com/api/v1/resolve?ref=hsuanyulee/polaris/review-pr GET https://markdownregistry.com/api/v1/blob/151030ff04952f258688de843505efa60e3ef7e6a08419d71bd7d3c618ff2c9b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from hsuanyulee/polaris
Every file in hsuanyulee/polaris