Skip to content
BENIBIX Learn

REVIEW.md vs CLAUDE.md

People think REVIEW.md and CLAUDE.md do the same job, since Code Review reads both. They do not. CLAUDE.md tells Claude about the project, and every Claude Code session reads it. REVIEW.md tells Code Review what to flag and what to skip, and only that service reads it. The review command you run in a terminal reads CLAUDE.md but not REVIEW.md. So put review rules in REVIEW.md.

AI⌨️ Claude Code

REVIEW.md

A file that tells Code Review what to flag and what to skip.

REVIEW.md is a file at the root of a repository that tells Code Review what to look for. It can say what to flag, at what level, and which paths to skip, such as files a tool makes for you. Code Review reads it along with CLAUDE.md. A subfolder can have its own REVIEW.md that adds checks for the code under it. The local /code-review command does not read it.

Example
Lucy's reviews keep flagging style nits in generated code. She adds REVIEW.md telling it to skip that folder, and the noise stops.
Why it matters
Each team cares about its own things. This file is how a review learns what yours are.
Full entry
AI⌨️ Claude Code

CLAUDE.md

A file of rules Claude Code reads each time it starts.

CLAUDE.md is a plain text file of instructions that Claude Code reads at the start of every session. You write it in Markdown. It can hold your build commands, your style rules and things to avoid. There can be one in your home folder for all projects, one in the project for the team, and more in sub-folders. Claude Code loads them all together. Running /init writes a first version for you by looking at your code.

Example
Emma's team keeps telling Claude to use their test command. She adds it to CLAUDE.md once, and every session after that uses it.
Why it matters
It is the easy way to stop saying the same thing in every session.
Full entry

In one line

REVIEW.md
A file that tells Code Review what to flag and what to skip.
CLAUDE.md
A file of rules Claude Code reads each time it starts.