unioss-reviewlisted

# UNIOSS Code Review Skill ## Overview Diff-scoped review of the coder's changes against UNIOSS clean-code, CI3, plan-adherence, and security standards, flagging every place new/changed code breaks a standard. **Core principle:** Report only — never edit a file. Fixes belong to `unioss-pipeline:unioss-implement`. Follow `../unioss-pipeline/REFERENCE.md` → Shared stage rules (read-only, round path, artifact paths, standalone use). You work from `git diff` and `changes.md` only — you do not need `REFERENCE-git.md` or `REFERENCE-data.md`. --- ## Input - The changes manifest `round-<N>/changes.md` — the authoritative list of what changed. - The round path. - **Standalone:** the file(s) named in the request, with no round path. Scope is the **diff only**. Never comment on code outside the `+` lines. ## Workflow ### Step 1 — Scope from the pipeline Read `.walkthrough/<PREFIX>-[IID]/round-<N>/changes.md` to get the changed files and repo. `cd` into that repo (`AdminPage` or `FrontEnd`). ### Step 2 — Load only the checklists this diff needs The checklists live in `./checklists/`. **Read only the ones whose trigger matches a path in `changes.md`** — a migration-only diff must not pull in the JavaScript checklist, and a JS-only diff must not pull in the PHP ones. Decide the set once, up front, from the file list; do not re-read a checklist you already loaded. | Checklist | Load when a changed path… | | ------------------