review-readiness-scan
SolidUse when 批次掃描多個 change 的 manual review readiness。NOT for 單一 change 逐項 review(走 pnpm review GUI)。
Web & Frontend 45 stars
3 forks Updated today MIT
Install
Quality Score: 87/100
Stars 20%
Recency 20%
Frontmatter 20%
Documentation 15%
Issue Health 10%
License 10%
Description 5%
Skill Content
<!-- 🔒 LOCKED — managed by clade · auto-generated by sync-to-codex; 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
- 7 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 Featured
nuxt-data-audit
Use when 審計 Nuxt 專案 data-fetching 模式與效能 golden path checklist。
45 Updated today
YuDefine Data & Documents Solid
data-sanity
Use when running Design Review, before delivering a work item for manual review, or ad-hoc on changes touching paginated queries. Detects client-server schema mismatch. NOT for 一般 code review(走 review-rules)。
45 Updated today
YuDefine Code & Development Solid
review-archive
Use when 人工檢查已結束需歸檔 review 結果 — spectra 流程自動觸發,或使用者要求歸檔 review。
45 Updated today
YuDefine