review-readiness-scan

Solid

掃描 openspec/changes/ 各 change 的 manual-review 區塊,判斷哪些已 ready for 人工檢查、哪些被 Pre-Review Data Readiness pattern 命中(alert)尚未 ready,並把結果登記到 HANDOFF.md。Use when 使用者說「掃 review readiness」「review:ui 哪些 ready」「scan manual review alerts」「批次人工檢查前先看哪些 ready」「找出 review:ui 的 alert」。不適用於單一 change 內逐項 review(那走 `pnpm review` GUI,從 clade home 跑)。

Web & Frontend 45 stars 2 forks Updated today MIT

Install

View on GitHub

Quality Score: 86/100

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

Skill Content

<!-- 🔒 LOCKED — managed by clade · auto-generated by sync-to-agents; edit source in .claude/ then re-run sync --> # review-readiness-scan 主動掃描 consumer 端所有 active change 的 `## 人工檢查` 區塊,把「已 ready / 尚未 ready」分組寫入 `HANDOFF.md`,讓使用者能在合適時機**批次**跑 `pnpm review`(從 clade home),而不是每條 change 個別開 GUI 才知道沒準備好。 **前置**:consumer 必須已從 clade 散播到 `scripts/review-gui.mts`(各 consumer 預設都有;若沒有,跑 `pnpm hub:check` 確認)。 ## Step 1 — 跑 headless scan ```bash cd ~/offline/clade node vendor/scripts/review-gui.mts --scan ``` 預設從 clade home 掃,輸出會聚合 `consumers.local` 內所有 consumer + worktree。若是 CI / debug 要只掃單一 consumer,才改用 `node vendor/scripts/review-gui.mts --repo <consumer-path> --scan`。 `reviewPort` 會用跟 GUI server 相同的 fallback 規則計算:若 5174 已被占用,scan 會輸出下一個可用 port(例如 5175),後續 handoff **MUST** 使用 entry 內的 `reviewUrl`,不要硬寫 5174。 輸出 JSON(schema: `review-readiness-scan/v2`)到 stdout,結構: ```jsonc { "schema": "review-readiness-scan/v2", "generatedAt": "<ISO8601>", "repoRoot": "<abs>", "reviewHost": "127.0.0.1", "reviewPort": 5174, "counts": { "ready": N, "notReady": M, "buckets": { "ready": N, "readyForEvidence": N, "applyInProgress": N } }, "ready": [ { "name": "<change>", "consumerId": "perno", "changeKey": "perno:<change>", "reviewUrl": "http://127.0.0.1:5174/review/perno:<change>", "bucket": "ready", "pending": N, "issued": N, "total": N } ], "notReady": [ { "name": "<change>", "consumerId": "perno", "changeKey": ...

Details

Author
YuDefine
Repository
YuDefine/nuxt-supabase-starter
Created
4 months ago
Last Updated
today
Language
JavaScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Listed

screenshots-archive

將已收錄到 docs/manual-review-archive.md 的 change,把對應截圖資料夾從 screenshots/<env>/<topic>/ 搬到 screenshots/<env>/_archive/YYYY-MM/<topic>/。讓 screenshots/<env>/ 頂層只剩 current pending review。觸發詞:歸檔截圖、sweep screenshots、清掉舊的截圖資料夾、screenshots archive。

45 Updated today
YuDefine
Code & Development Listed

review-archive

將已完成的人工檢查項目從 tasks artifact 遷移到 docs/manual-review-archive.md,保留追溯資訊。

45 Updated today
YuDefine
Code & Development Listed

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 yesterday
HsuanYuLee
AI & Automation Listed

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 yesterday
HsuanYuLee
Web & Frontend Listed

second-opinion

獨立 code review — 從全新視角檢查

45 Updated today
YuDefine