Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.227 Home All releases ←olderv2.1.226 v2.1.228newer→
Claude Code v2.1.227

/ultrareview can post its findings to a GitHub pull request

Use it now
Useful4 Signal3
Code Review Notable

/ultrareview takes --post and --no-post to comment findings on a GitHub PR as you.

Feature flag
tengu_ultrareview_post_enabled Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.227: off

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.227. It isn't a statement about your account. What a flag value here can and cannot tell you

/ultrareview--post--no-post
What

/ultrareview and claude ultrareview now take --post and --no-post. With posting armed against a GitHub.com pull request, the finished review is posted as a single plain comment from your own GitHub account, not as a formal review. Posting is gated on tengu_ultrareview_post_enabled (falls back to on); when it resolves off the CLI replies that posting findings to the PR is currently turned off. Consent is session-scoped: end the session before the review finishes and nothing is posted.

Details
  • Interactive runs still confirm in the launch dialog, which gains a proceed-post choice described as "Post the finished review's findings to the PR as you (PR targets only; one plain comment, not a review)". Non-interactive runs post on the flag alone.
  • The task carries the target repo and PR number, and on completion a separate cloud job runs a locked-down posting prompt that calls get_me and then add_issue_comment exactly once.
  • Non-GitHub.com targets and non-PR scopes print Note: --post was ignored and continue, explaining that posting applies only to GitHub.com pull request reviews.
  • Progress prints "Posting now — a single plain comment, not a review."; a failed review prints "Nothing was posted to the pull request: the review failed."
Usage
claude ultrareview --post
claude ultrareview --no-post
Evidence

"--no-post", Post the finished review's findings to the PR as you (PR targets only; one plain comment, not a review), postReviewToPR, Nothing was posted to the pull request: the review failed.

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.227 →