review-inbox

Solid

Use when the user wants to discover and review PRs across the team awaiting their attention. NOT for a single specific PR (use review-pr). Supports three discovery modes: Label (GitHub label scan), Slack (channel-wide scan), Thread (specific Slack thread URL). Trigger: '掃 PR', 'review 大家的 PR', '批次 review', '有哪些 PR 要我看', Slack thread URL + review intent ('review <slack_url>', '幫我看這串'). Key: '我的 PR' → check-pr-approvals; '大家的 PR' / Slack URL → here; single PR URL → review-pr.

Code & Development 4 stars 0 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
23
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Review Inbox — 批次 Review 待審 PR 找出 team 內需要自己 first review、re-approve、或 re-review 的 PR,批次執行 review, 並依來源回 Slack 通知。 ## Contract 此 skill 只處理多 PR discovery + batch review orchestration。單一 PR URL 轉 `review-pr`; 「我的 PR」approval 狀態轉 `check-pr-approvals`。 支援三個來源: | Source | Use when | |---|---| | Slack | 預設;掃 PR channel 最近訊息中的 PR URLs | | Thread | 使用者提供 Slack thread URL 並要求 review | | Label | 使用者明確提到 need review label | 不得 review 自己的 PR。不得對 `waiting_for_author` PR 重複 review。 Review inbox 屬 reviewer-side read-only lane;它可以 advisory,但對 `awaiting_re_review`、 `mergeable_ready`、`unsupported_mutation`���`changes_requested` 的解釋必須沿用 shared PR state。 它不得把 batch review 結果升格成 author-side completion / release authority;所有 「可 merge / 已修完 / 可 release」語句只能轉述 shared state,不可自行推論。 ## Reference Loading | Situation | Load | |---|---| | Any run | `context-budget-contract.md`, `review-inbox-discovery-flow.md`, `shared-defaults.md`, `stale-approval-detection.md`, `workspace-config-reader.md` | | Batch review execution | `review-inbox-batch-review-flow.md`, `review-inbox/dispatch-context-bundle.md` | | Slack notification | `review-inbox-slack-reporting.md`, `slack-message-format.md`, `github-slack-user-mapping.md`, `workspace-language-policy.md` | Slack channel scan 可以派 read-only sub-agent。Per-PR review 不得使用 Claude Code general-purpose sub-agent;只有 runtime 提供 constrained code-reviewer adapter 時才可平行 dispatch。否則依 `build-review-runtime-plan.py` 產生的 `main_session_sequential` plan,一次執行 一個 review pac...

Details

Author
HsuanYuLee
Repository
HsuanYuLee/polaris
Created
4 months ago
Last Updated
3 days ago
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

review-pr

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 REQUEST_CHANGES. 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 for "請<同仁/大家/人名>幫我 review" (subject = others) — that is 催 review, route to check-pr-approvals. NOT for "review 大家的 PR" / "掃 PR" (object = others' PRs) — route to review-inbox. NOT for fixing review comments on your own PR — route to engineering revision mode. (use engineering revision mode for that).

4 Updated 3 days ago
HsuanYuLee
AI & Automation Solid

check-pr-approvals

掃描使用者的 open PR,偵測 CI 狀態、未回覆 review comments、approval 數量,分類為三種狀態(可催/需修/已達標)後由使用者選擇催 review 或手動修正。Trigger: '我的 PR', 'check PR approvals', 'PR 狀態', '催 review', '催 PR', 'PR 被 approve 了嗎', '幫我掃我的 PR', '請同仁 review', '請同仁幫我 review', '請大家 review', '請大家幫我 review', '請大家幫忙看一下', '找人 review', '找誰 review', '請[人名/角色]幫我 review', '請[人名/角色]幫忙看 PR'. 主語為同仁/大家/人名/角色的「請X幫我 review」屬於催 review 範疇,不要 route 到 review-pr。

4 Updated 3 days ago
HsuanYuLee
AI & Automation Solid

pr-pickup

Slack collaboration layer: extracts PR URLs from Slack messages and dispatches to engineering revision mode. Does NOT modify code — all code changes, GitHub review replies, and lesson extraction are engineering's responsibility. 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), first-cut implementation (use engineering directly), fixing your own PR without Slack context (use engineering with ticket key or PR URL directly).

4 Updated 3 days ago
HsuanYuLee