README

Usage

• PR# or PR URL: the pull request to review, by number or full URL
• --base <ref>: for local changes only, the ref the branch is diffed against instead of origin/HEAD. Use the remote-tracking form (origin/rc): a bare rc needs a local branch of that name, which can sit behind the remote. Dropped with a pull request target, where GitHub’s recorded base is used. The ref must match ^[A-Za-z0-9][A-Za-z0-9._/-]*$
• --output-dir <path>: directory for the review files. Defaults to ${CLAUDE_PLUGIN_DATA}/code-reviews/
• No arguments: the command asks whether to review a pull request or the local changes

Only the space-separated forms are accepted. --base=rc, --output-dir=foo, or a flag with no value is refused before the review starts.

Examples

For local changes the agent reviews one scope, not both: the branch against its base when it has commits ahead of that base, otherwise your pending changes (tracked edits plus untracked source files). To review uncommitted edits on a branch that is already ahead of its base, commit them first and re-run. The summary names the scope and the base it used. A --base ref that does not resolve produces a No Verdict rather than a review of some other scope.

Output files

The agent, not this command, decides where the files go and what they are called; the command only passes --output-dir through. The agent flow diagrams (opens in a new tab) show the rule.

Both land in ${CLAUDE_PLUGIN_DATA}/code-reviews/, or in --output-dir when given, and the command prints the full path of each. Writes under ~/.claude/ ask for approval, so headless runs (claude -p) need --output-dir set to an allowed directory.

Summary file. The summary comment, in the format posting-review-summary posts to GitHub:

When nothing could be reviewed it carries the NO VERDICT form instead, with the reason in place of the assessment sentences.

Inline-comments file. Every inline comment the agent would have posted, with file and line references. Empty when there are none.

Posting a reviewed draft

Requirements

• GitHub CLI (gh) installed and authenticated, for pull request targets
• The bitwarden-code-review plugin installed

Related documentation

• Bitwarden Code Review Plugin README (opens in a new tab)
• Bitwarden Code Reviewer Agent (opens in a new tab)
• Code review agent flows (opens in a new tab)