# Code Review

> Use when reviewing code changes, a pull request, or a build slice for blockers before approval — correctness, security, scope, consistency, and test coverage. Activates on "review this", "is this ready", "check this PR/slice", or the Orchestrator REVIEW step.

- Skill: `tomevault-io/code-review-231` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/code-review-231`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/code-review-231/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/code-review-231

---


# Code Review

Blocker-first review. Lead with what must change, not with praise.

## Procedure

1. Restate the slice's acceptance criteria from the approved spec. If none are
   visible, stop and ask for them — do not review against a guessed intent.
2. Walk the diff and classify every finding as **BLOCKER**, **SHOULD**, or
   **NOTE**. Only BLOCKERs gate approval.
3. Check, in this order:
   - **Correctness vs spec** — does it meet each acceptance criterion?
   - **Evidence discipline** — no invented package facts; inference labeled;
     missing evidence explicit. (See the `evidence-discipline` skill.)
   - **Security** — no secrets/keys/`.env`; input validated at boundaries;
     no command/SQL injection or unsanitized interpolation.
   - **Scope** — nothing beyond the spec (no speculative abstractions,
     features, or error handling for impossible cases).
   - **Consistency** — matches existing patterns and the language's modern
     idioms; names carry intent; no dead/half-finished code.
   - **Tests** — behavior is covered; determinism where relevant; no live
     APIs in unit tests; pass/fail reported truthfully.
4. Output: a pass/fail verdict, then the BLOCKER list with `file:line` and the
   specific required change, then SHOULD/NOTE items.

## Constraints

- Do not modify application code in this pass; produce the blocker list.
- Do not approve with open BLOCKERs.
- No overclaim language in the review summary.

---
> Source: [ChiromboKenT/oss-preflight](https://github.com/ChiromboKenT/oss-preflight) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->

