← ClaudeAtlas

rite-reviewlisted

Review polished feature diff for correctness, readability, architecture, security, tests proving acceptance, Critical/Important findings, and quality dimensions before seal.
ViktorsBaikers/DevRites · ★ 1 · Code & Development · score 63
Install: claude install-skill ViktorsBaikers/DevRites
# /rite-review: feature-scoped review Review the **active feature scope only**. **Read the active workspace first**; if none, tell the user to run `/rite-spec <feature>`. > **Scope:** `/code-review` is a generic diff review with no workspace context. > `/rite-review` reads > `.devrites/work/<slug>/spec.md` first, runs Spec ↔ Code-review axes as > parallel fresh-context reviewers (see [`parallel-dispatch.md`](../devrites-lib/reference/parallel-dispatch.md)), and gates feeding > into `/rite-seal`. Use `/code-review` for a one-off diff; use > `/rite-review` for a DevRites feature where the spec is the contract. ## Rules consulted (read on demand from `.claude/skills/devrites-lib/reference/standards/`) Pull these via `Read` when the diff demands them: - `code-review.md`: small PRs, severity labels, tests-first review focus. - `review-checklist.md`: compact pass/fail sweep before reporting the verdict. - `principles.md`: declared project invariants (`.devrites/principles.md`); a diff that violates one with no recorded exception is a Critical, blocking finding. - `testing.md`: confirm that passing tests actually prove the spec. - `agents.md`: when to fan out to which review subagent. - `security.md`: when input / auth / data / integrations / secrets are in scope. - `security-checklist.md`: for the same security-sensitive scope, the compact trust-boundary sweep. - `performance.md`: only when perf is relevant or a regression risk is visible. ## Operating rules - **Feature scope o