A review workflow that checks completed work against code, specifications, designs, or functionality. It can identify the review type from the latest task in the development plan.

Use it to review backend or frontend code, API and data specifications, UI designs, tests, documents, or other completed sprint tasks.

It gives reviews a consistent checklist and records the result in the sprint plan. This helps catch implementation, documentation, design, and specification mismatches.

review — Skill for Claude Code by Stanshy: A review workflow that checks completed work against code…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/stanshy/agenthub/review

Any agent

npx skills add Stanshy/AgentHub --skill review

Clone the repo

git clone --depth 1 https://github.com/Stanshy/AgentHub

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/stanshy/agenthub/review.svg)](https://agentmods.dev/skills/stanshy/agenthub/review)

Your own site

<a href="https://agentmods.dev/skills/stanshy/agenthub/review"><img src="https://agentmods.dev/badge/skills/stanshy/agenthub/review.svg" alt="Measured on agentmods" height="20"></a>

Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,921 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00018	$0.01921
Opus 5	$0.00009	$0.00960
Sonnet 5	$0.00004	$0.00384
Haiku 4.5	$0.00002	$0.00192

Measured 6d ago against content hash 486f77bbc4f6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.knowledge/company/skill-templates/review/SKILL.md · 132 lines

How it starts

The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.

L1 內部 Review

執行內部 Review checklist 並記錄到開發計畫書第 10 節。支援自動偵測步驟類型。

使用方式

/review [review-type] [target]

參數

$0: Review 類型（auto / code / spec / design / function）
$ARGUMENTS: 完整參數
若 $0 為 auto 或省略，自動偵測當前步驟

步驟自動偵測

當 review-type 為 auto 或未指定時：

讀取 proposal/sprint*-dev-plan.md（最新的開發計畫書）
找到第 10 節「執行紀錄」中最近完成的任務
根據任務類型判斷步驟：
- 含 design / 架構 / API 設計 → 步驟 = 設計 → Review: 對規範
- 含 mockup / UI / 圖稿 → 步驟 = UI 圖稿 → Review: 對設計稿
- 含 backend / API / route / service → 步驟 = 實作（後端）→ Review: 對程式碼 + 對規範
- 含 frontend / component / view / page → 步驟 = 實作（前端）→ Review: 對程式碼 + 對設計稿 + 對規範
- 含 test / e2e / spec → 步驟 = 測試 → Review: 對功能 + 對規範
- 含 doc / 文件 → 步驟 = 文件 → Review: 對規範
輸出偵測結果，確認後執行

Review Checklist

對程式碼（code）

無 bug 或邏輯錯誤
錯誤處理完整（外部呼叫有 try-catch）
無硬編碼機密資訊
命名有意義且符合規範（snake/camel/Pascal 分層）
無死碼（註解掉的程式碼、未使用的 import）
單一職責原則
TypeScript 型別正確（無 any）
文件已同步更新（.knowledge/ + CLAUDE.md 索引）

對規範（spec）

實作與 API 規範文件一致（api-design.md）
實作與 data model 文件一致（data-model.md）
實作與 feature spec 一致（feature-spec.md）
命名轉換正確（DB snake → API snake → 前端 camel）

對設計稿（design）

佈局結構一致（元件位置、大小、間距）
色彩一致（使用設計稿色系，未自行選色）
動畫一致（時長、easing 與設計稿規格相符）
狀態切換完整（設計稿定義的每個 UI 狀態都已實作）
響應式一致（桌面版和手機版都與設計稿一致）
文案一致（按鈕文字、placeholder、空狀態文案）

L1 比對方式：同時開啟設計稿 HTML/截圖和實際畫面，逐項確認。UI 不一致 = Blocker。

對功能（function）

端到端功能正常
效能達標
驗收標準全部滿足
無 Critical/High 等級 Bug

對文件正確性（doc-integrity）

檢查 dev-plan 和 .tasks/ 檔案的格式與內容一致性。 觸發時機：每次 /review 時自動附加執行，不需手動指定。

dev-plan 檢查

第 10 節存在且包含三個子表格（任務完成紀錄、Review 紀錄、Gate 紀錄）
Gate 紀錄的決策值符合規範（✅ 通過 / ❌ 駁回 / ⚠️ 附條件通過，不可用純文字或英文）
日期格式為 YYYY-MM-DD
第 6 節任務表與 .tasks/ 目錄的任務數量一致

task 文件檢查（逐一掃描 `.tasks/sprint-{N}/*.md`）

metadata 表必要欄位齊全：ID、狀態、Sprint、建立時間、開始時間、完工時間
狀態值為合法英文值（created / assigned / in_progress / in_review / done / blocked / rejected）
事件紀錄區塊（## 事件紀錄）存在且至少有一筆紀錄
事件紀錄 timestamp 格式為 ISO 8601（YYYY-MM-DDTHH:mm:ss.sssZ）
狀態為 done 的任務，驗收標準全部打勾（- [x]，無殘留 - [ ]）
狀態為 in_progress 以上的任務，開始時間 不得為 —
狀態為 done / in_review 的任務，完工時間 不得為 —

Read the full file on GitHub · 132 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

6d ago First seen · 132 lines · 18 tokens per session scan A 486f77bbc4f6

Subscribe to this mod's changes

review is a skill published in the GitHub repository Stanshy/AgentHub (201 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 1,921 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code review ai-agents ai-workflow claude-code developer-tools electron harness-engineering

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

integrated-browser

Use this when working on the VS Code integrated browser ("browserView") to understand its architecture and mental model. Covers the embedded Chromium browser, its editor tab, navigation, overlay/layout, sessions, and agent browser tools under src/vs/platform/browserView and src/vs/workbench/contrib/browserView.

microsoft/vscode · 68 tokens

generate-run-commands

Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.

microsoft/vscode · 36 tokens

thisWeek

Resolve "thisWeek" to a concrete ISO date range relative to your run time — this week so far (Monday → today). Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a week-to-date task (this week's activity…

chaitanyagiri/munder-difflin · 77 tokens

comet-design

Comet Classic 阶段 2 —— 为 change 产出深度技术 Design Doc。.

rpamis/comet · 24 tokens

comet-verify

Comet Phase 4: Verify and Close. Invoke with /comet-verify. Verify implementation matches design, handle development branch.

rpamis/comet · 32 tokens