reviewlisted

This skill is the **review** orchestrator. It runs the two reviews — technical, then visual — against the code produced by `/build`, using the docs from `.design/<slug>/` as the yardstick. The three-part pipeline: - `/design` — produces docs in `.design/<slug>/`. - `/build` — reads those docs, writes the code. - `/review` — this skill. Reviews the code against the docs. ## Prerequisites Both are needed: - `.design/<slug>/` with at minimum `DESIGN_BRIEF.md` (the intent to measure against). - Code changes to review — either uncommitted, on a branch diff, or in files the user names. If there's no design folder, tell the user to run `/design` first (or point at a brief). If there's no diff, ask which files to review. ## The Sequence ``` 1. Code Review → .design/<slug>/CODE_REVIEW.md (correctness / security / tests / clarity) 2. Design Review → .design/<slug>/DESIGN_REVIEW.md + screenshots (visual / aesthetic / responsive) ``` Both phases read from the same `.design/<slug>/` folder and write their reports back into it. ## Operating Rules 1. **Open with a scan.** Ask (or infer) which feature slug this review is for. List what's in `.design/<slug>/`. Show a git diff summary (files changed, lines added/removed). Ask which phases to run — usually both, but code-only or design-only is fine. 2. **Announce each phase before entering it.** Format: "Phase N: [name]. This checks [what]. Ready?" Wait for confirmation. 3. **Run each phase by reading its SKILL.md an