Skip to content

Dev: Add REVIEW.md with review priorities for Claude Code Review - #1041

Merged
epeicher merged 1 commit into
trunkfrom
dev/review-md
Oct 22, 2026
Merged

epeicher merged 1 commit into
trunkfrom
dev/review-md

Conversation

@epeicher

@epeicher epeicher commented Oct 22, 2026 •

Copy link
Copy Markdown
Collaborator

What it does

Adds a root REVIEW.md, the file Claude Code Review reads to decide what to flag on a pull request, at what severity, and what to skip. It changes nothing until the Code Review service is enabled for this repository.

Rationale

AGENTS.md says what the rules are. It doesn't say which broken rule should block a merge and which is a nit, so a reviewer weighs every rule the same. Most PRs here are written by agents, so each nit costs another commit and another review round. The file applies the guidance from Anthropic's write-up of their own review setup: keep it short, say what failure looks like in this repo, cap the nits, list paths to skip, require evidence, and fix the summary format.

Implementation

  • What failure looks like, ranked by cost: it leaks, it loses data, it breaks a plugin author, it stops updating live.
  • What 🔴 Important means: those four classes plus wrong logic, unescaped HTML, and unreachable controls. Style is 🟡 Nit at most.
  • Always check: 12 repo rules, each citing its AGENTS.md section instead of restating it. The list includes the read-path gates, frozen desktop_mode_* names, assets/js/ build output, the Legacy snapshot, cross-bundle state, settings that need a menu refresh, docs that no longer match the code, and the palette rules for feature stylesheets (which no test sweeps).
  • Do not report: anything CI enforces, built and vendored files, languages/, lockfiles, missing test coverage, and file-length warnings. A higher bar applies in bin/, tools/, reports/, extensions/ and tests/.
  • Converging: a file:line for every finding, at most three Nits, one finding per bug class, no repeated findings on a re-review, and a summary that opens with the counts.

How the service reads the file:

  • Source branch. The service reads REVIEW.md from trunk, never from the PR's own changes, so edits to this file apply only after it merges. Because trunk is protected, the instructions that lower a severity, skip paths or cap nits are all honored.
  • No Markdown links. The file uses none, on purpose: past 64 links the service ignores the whole file. That limit is also why it doesn't @-include AGENTS.md.
  • Not the @claude workflow. claude.yml runs Claude Code itself, which loads CLAUDE.md but not REVIEW.md. Neither does the local /code-review command.
  • Not shipped. bin/package.sh is an allow-list, so the file stays out of the release zip.

Testing instructions

Nothing to run locally. Once Code Review is enabled for the repository, comment @claude review on an open PR. Each finding should carry a 🔴/🟡/🟣 label, the review should post at most three Nits, and the summary should open with a line like 1 Important, 2 Nit, 0 Pre-existing.

Open WordPress Playground Preview

Tells the Code Review service what failure looks like in OpenStation,
what counts as Important, which rules to check on every pull request,
what to skip, and how to keep review rounds converging. The rules point
at their reasoning in AGENTS.md instead of restating it.
@epeicher
epeicher merged commit dd3f3a8 into trunk Oct 22, 2026
7 checks passed
@epeicher
epeicher deleted the dev/review-md branch October 22, 2026 16:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant