pr-pickup SKILL.md skillA
pr-pickup 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/pr-pickup@v1.0.0Pins v1.0.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/pr-pickup/SKILL.md- Versions recorded
- 5
- Latest version
- v1.0.0, committed Sep 3, 2026
- First version recorded
- Aug 8, 2026
- Size
- 8,487 bytes
- Repository stars
- 5
- License
- MIT
Slack collaboration layer: extracts PR URLs from Slack messages, hands the PR over to be fixed, then reports back to the thread. Owns the Slack half only — it does not read review comments and does not modify code. Trigger: "pr-pickup", "pickup", Slack URL + PR intent ("pickup <slack_url>", "處理 <slack_url>", "同仁貼的 <slack_url>", "接這個 PR <slack_url>"). NOT for: reviewing others' PRs (use review-pr), or fixing your own PR when nobody is waiting on a Slack thread — then just fix it, no relay needed.
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
# pr-pickup 從 Slack 訊息擷取 PR review 請求，把 PR 交出去修，完工後回 Slack thread 告知結果。 **職責邊界**：pr-pickup 只做協作傳遞（intake → 交付出去 → broadcast）。不讀 review comments、不改 code、不回覆 GitHub review。修 PR 這件事本身不歸它——那多半不用立案（改的是既有 assertion 底下的做法），直接修；若連成功的定義都要改，那是 `refinement` 的事。 它的 shared authority 應收斂在 intake artifact，而不是 prose 解析。Slack/PR 輸入的 canonical 解析結果由 `$SKILL_DIR/scripts/resolve-pr-pickup-input.sh` 定義；skill 只消費該 artifact，不能再手工 各寫一套 PR URL / thread context 判斷。 ## 前置：這條線在哪個 org `resolve-pr-pickup-input.sh` 讀 Slack thread 的時候要 `--org`，因為它要在那一串裡找出屬於 那個 org 的 PR URL。**那個值問 `request-pr-review` 帶的那支命令**，它列出這台機器上被宣告 的每一個 org： ```bash bash "$SKILL_DIR/../request-pr-review/scripts/resolve-pr-context.sh" orgs ``` 只有一個就用它，不只一個就從那串訊息裡的 PR URL 判。**這裡不寫任何設定鍵**：org 是誰宣告 的、宣告在哪，由那支命令回答，這一支不認得任何一家公司。 以前這裡寫「讀 workspace config，本步驟需要的值：`github.org`、`slack.channels.ai_notifications`」 ——兩個鍵在任何一份 `workspace-config.yaml` 裡都不存在，`$GITHUB_ORG` 整支 skill 沒有人賦值， 而 `slack.channels.ai_notifications` 從頭到尾沒有任何一行讀它。 ## Bundled Authority | Script | Role | |---|---| | `$SKILL_DIR/scripts/resolve-pr-pickup-input.sh` | canonical intake resolver：統一解析 direct PR URL、Slack URL、Slack thread context、以及 thread-derived PR URLs | ## 流程總覽 …
Read the whole file at its exact version.
How to install
mdr add hsuanyulee/polaris/pr-pickup@sha256:605d5361566ce004The line at the top of this page pins the label v1.0.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_wdakl3yr6i7pwywi)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 8, 2026 and Sep 3, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-09-03 | 910b3a3 | 8,487 B | A | view · diff |
| v1.0.0 | 2026-08-29 | 4754d29 | 7,451 B | A | view · diff |
| v1.0.0 | 2026-08-24 | e610d9d | 7,431 B | A | view · diff |
| v1.0.0 | 2026-08-09 | 834f192 | 7,432 B | A | view · diff |
| v1.0.0 | 2026-08-08 | af2f973 | 7,414 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 (8487 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_wdakl3yr6i7pwywi GET https://markdownregistry.com/api/v1/resolve?ref=hsuanyulee/polaris/pr-pickup GET https://markdownregistry.com/api/v1/blob/605d5361566ce004eae6cdcd3bad8bc6cfa80ecf35bd90aada888d1d3531ff6e
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.