← ClaudeAtlas

rjv-code-reviewlisted

Review a code change, a proposed fix or a design for behavioral regressions, especially when a prior review missed a bug. Also runs the round-numbered review loop: Claude writes a brief file for Codex or opencode, the user relays it, the reviewer writes a result file, every path absolute. Use for PR reviews, design reviews, follow-up review rounds, writing a review brief, reading a review result, and claims that a fix is clean. Works in Claude Code and Codex.
rjvim/ai-skills · ★ 0 · Code & Development · score 61
Install: claude install-skill rjvim/ai-skills
# Code review: prove the neighboring behavior Review the behavior users can reach. A passing test and a plausible diff do not prove that an old path still works. Load the repository's domain and product review skills too when the change touches their area. A review is read-only: edit, stage or commit nothing in the repo. The only file you write is the result file or the reply. A stated scope limits what you report on. It does not limit what you read. When an existing rule, producer or feature the change depends on sits outside the scope, read it anyway and report the gap as a finding: "the brief put X out of scope, and the change depends on it". **Base a clean verdict only on code you read**, never on code the scope told you to skip. When you run the review loop with Codex or opencode (writing a round brief, reading a round result, or cleaning up the round files under `~/.reviews/`), read [`ROUNDS.md`](ROUNDS.md). **Never start a reviewer (Codex or opencode) yourself unless the user asks in this session or the plan's Cast (`rjv-gated-build`) names a self-started reviewer**; otherwise the user relays each file by hand. ## Before judging the diff 1. State the behavior the change promises and the old behavior it must preserve. 2. Trace each changed route or entry point through its caller, state read, decision, write, and downstream reader. Include unchanged files that are load-bearing in that chain, including any outside the requested scope. 3. Search for an existing featur