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 below. **Core principle:** Report only — never edit files, unless the user explicitly follows up with `fix #N`. **Track progress:** create a todo per Workflow step below and check each off as you complete it. Follow `../unioss-pipeline/REFERENCE.md` → Shared stage rules (read-only, round path, artifact paths, standalone use). --- ## 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 — Read the diff ```bash git diff # working-tree changes from the coder stage ``` Judge `+` lines for the quality of new/changed code. Do **not** ignore `-` lines — each removal is a change with consequences. Whenever the diff deletes a referenceable symbol (a constant, function/method, class, DB column, route, config key, parameter, or a guard/branch), grep the repo for surviving references — e.g. `grep -rn "REMOVED_NAME" AdminPage FrontEnd` — and flag any remaining us