reviewlisted

# Review Front door for review, the way `scope` is the front door for work that isn't ready to build. Classify what is in front of it, announce the route, invoke that route's skill. This skill does none of the reviewing itself — the standards-and-spec pass it used to run now lives in `code-review`. ## Routes Routes are data, not prose, layered from two files: - **Shipped:** [`routes.json`](routes.json) in this directory. Four rows ship today: - `code` → `code-review` — changed code against the repo's documented standards and the originating issue. - `plan` → `plan-review` — a plan, spec, work order, or agent brief, before anything is built. - `personas` → `persona-review` — a document that needs named reviewer perspectives. - `security` → the security review that ships with the agent — pending changes carrying a security question. - **Operator:** `~/.config/review/routes.json`. A row whose `route` matches a shipped row replaces it; any other `route` extends the table. See *Registering a review type* below. ## Process 1. **Classify.** Read what's in front of you — a diff, a document, the user's own words — and pick the route whose `for` text matches it. 2. **Announce.** Say the route in one line before invoking anything: "routing to `code-review`" or equivalent. This is how the caller knows which review ran, not a request for approval. 3. **Invoke.** Call that route's skill (or, for `security`, the agent's built-in security review)