check-pr-approvals

Solid

掃描使用者的 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。

AI & Automation 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

# Check PR Approvals — PR Review 進度追蹤 掃描 `{config: github.org}` org(fallback: `your-org`)下指定使用者的 open PR,偵測 rebase、CI、review comments、approval / stale approval,並用 shared PR state vocabulary 做分類後等待使用者選擇下一步。 核心邊界:本 skill 只偵測、分類、呈報與在使用者選擇後通知 reviewer;不自動修正 CI failure、review comments 或 rebase conflict。需修正的 PR 交給 `engineering`。 ## 前置 讀取 workspace config(見 `references/workspace-config-reader.md`),需要: - `github.org` - `slack.channels.ai_notifications` - shared defaults:approval threshold、review label、fallback org/channel 若使用者沒有指定 author,先執行: ```bash MY_USER="$(gh api user --jq '.login')" ``` ## Bundled Scripts Script 路徑相對於本 skill 目錄。執行前確認有 `+x` 權限。 | Script | 用途 | Output contract | |--------|------|-----------------| | `scripts/fetch-user-open-prs.sh` | 搜尋 author open PR,含 base/head/labels | PR JSON array | | `scripts/rebase-pr-branch.sh` | 批次 rebase PR branches | 加上 `rebase_status` | | `scripts/fetch-pr-review-comments.sh` | 批次取得未回覆 actionable comments | 加上 `actionable_comments` | | `scripts/check-pr-approval-status.sh` | 批次檢查 approvals / stale | 加上 approval fields | Script 是 deterministic source;不要在入口重寫其內部 API / stale / bot filter 邏輯。PR type、mergeability、base_freshness、`awaiting_re_review` / `mergeable_ready` 語義以 shared PR state contract 為準。本 skill 只能偵測與轉述 shared state,不得把 bucket 名稱包裝成 author-side completion / release authority。 ## Lazy-load Map | 何時讀 | Reference | 用途 | |--------|-----------|------| | 產出分類報告、加 label、送 Slack、處理需修正 PR 時 | `references/check-pr-approvals-...

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
Code & Development Solid

review-inbox

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.

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