Menu
Per-BUILD-task reviewer: runs §1 static + §3 functional against REVIEW_RULE, writes the paired REVIEW-NNN.md.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Per-issue SDD cycle: resolve a PM issue to its TASK spec, plan a BUILD/REVIEW pair, build per FRONTEND_RULE_COMMON, review via the review skill.
Use when medium-to-large work needs requirements, design, task planning, readiness checks, and implementation governance before coding. Language-neutral.
發佈 @asgard-js/core 和 @asgard-js/react 的 canary 版本到 npm
| name | review |
| description | Per-BUILD-task reviewer: runs §1 static + §3 functional against REVIEW_RULE, writes the paired REVIEW-NNN.md. |
| version | 1.0.0 |
| alwaysApply | false |
/review BUILD-NNN to review a specific BUILD task/review all to review every BUILD task with Status = done in requirements/tasks/_index.mdRead requirements/tasks/_index.md Config block and extract SPEC_DIR (the directory where BUILD/REVIEW task files live; typically requirements/tasks/).
| Invocation | Scope |
|---|---|
/review BUILD-NNN | [BUILD-NNN] |
/review all | all Task Queue rows matching BUILD-* with Status = done |
Open {SPEC_DIR}/BUILD-NNN.md, read ## Coverage:
—].tsx / .ts paths]If either Coverage.Files or Coverage.Use Cases still contains the placeholder token [filled during build], stop immediately and report:
BLOCKER: BUILD-NNN is unfinished — Coverage still shows [filled during build].
Run the BUILD task to completion before invoking /review.
Do not proceed to §1 or §3.
| Section | Condition |
|---|---|
| §1 Static Code Review | Always |
| §3 Functional Validation | Coverage.Use Cases ≠ — |
This project's review procedure has exactly two sections: §1 and §3.
Follow REVIEW_RULE.md §1 procedure in full.
Scope for grep checks (§1.1 / §1.2): restrict to the directories / files listed in Coverage.Files. If no explicit directory is listed, fall back to src/.
tsc and lint always run project-wide (cannot be scoped per file):
npx tsc --noEmit
npm run lint:check
Write results under ## §1 Static Code Review in REVIEW-NNN.md:
tsc / lint:check outcomesIf any ❌ is found → mark as BLOCKER in ## Findings and do not mark REVIEW-NNN done until resolved.
—)Follow REVIEW_RULE.md §3 procedure in full.
Preferred harness: if an e2e spec exists for the changed routes, run:
npm run test:e2e
(Requires e2e/.env.local filled — see CLAUDE.local.md for E2E_USERNAME, E2E_PASSWORD, E2E_WORKSPACE_ID.)
If no matching e2e spec exists, manually validate each R# acceptance criterion in the browser against the running dev server (npm run dev -- -p <本地 dev port，見 CLAUDE.local.md>).
Write results under ## §3 Functional Validation in REVIEW-NNN.md using the R# Result Matrix from _review_template.md.
If any R# Fails → report BLOCKER; describe [actual behavior] vs [expected behavior].
If Coverage.Use Cases = —, write under ## §3 Functional Validation:
_skipped — Coverage.Use Cases is `—`_
If REVIEW-NNN.md does not yet exist, copy requirements/tasks/_review_template.md to {SPEC_DIR}/REVIEW-NNN-<slug>.md and fill the Meta block (Task ID, Status: in-progress, BUILD Task, reviewed commit, reviewed branch).
Fill each section with findings from Steps 3d–3e.
On completion:
Status: in-progress → done (only if zero BLOCKERs remain)## Execution Log with a one-line summary per section (sections run, pass/fail counts, final status)_index.mdMark REVIEW-NNN as done in the Task Queue.
tsc and lint:check still run project-wide.[filled during build] is present anywhere in Coverage, the BUILD is not done — report BLOCKER and stop.## Meta - BUILD Task in the REVIEW file.npm run lint:check (read-only) for review; npm run lint has auto-fix side effects.CLAUDE.local.md (e.g., npm run dev -- -p <port>).