reviewing-codelisted

# Reviewing Code Structured review methodology producing consistent, severity-based, actionable feedback. This skill defines the **review process** — how to conduct a review, format findings, and decide; the **what to look for** lives in perspective reference files the orchestrator loads selectively. Non-code artefacts use assessing-quality (rageatc-core-oss); architecture design review is the critic's job at architecture approval. ## Perspective Model Perspectives are reference files under `references/` defining what to examine. The orchestrator tells the reviewer-agent which to load. | Reference | Focus | Typical use | |-----------|-------|-------------| | `references/spec-compliance.md` | Does code match the brief and acceptance criteria? | All tiers — always loaded | | `references/code-quality.md` | Correctness, simplicity, readability, test quality | Standard + Thorough | | `references/security.md` | Input validation, injection, auth, data exposure | Thorough, or when chunk handles user input | | `references/whole-project.md` | Full codebase against PRD success criteria | End of Standard/Thorough build only | | `references/design-compliance.md` | UI matches system.md tokens, depth, patterns | Standard + Thorough, when project has system.md and chunk touches UI | **Tier defaults** (orchestrator may override — e.g., security for a Quick auth fix): | Tier | Perspectives loaded | |------|--------------------| | Quick | spec-compliance | | Standard | spec-compliance → c