{"version":"2.1.323","anchor":"ultrareview-can-send-a-draft-reviewmd-to-cloud-sessions-wi","canonical_anchor":"ultrareview-can-send-a-draft-reviewmd-to-cloud-sessions-wi","heading":"Ultrareview can send a draft REVIEW.md in place of the repository's own","tier":"use","area":"Code Review","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/ultrareview-can-send-a-draft-reviewmd-to-cloud-sessions-wi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Ultrareview can send a draft REVIEW.md in place of the repository's own\n\nA hidden --review-md option and CLAUDE_CODE_ULTRAREVIEW_REVIEW_MD_FILE send a draft REVIEW.md to each ultrareview session, with a checked preview first\n\n**What**\n\nUltrareview runs code reviews in cloud sessions. Its evaluation runner can now send a draft REVIEW.md file to every review session, to be used in place of the REVIEW.md the repository may already have. Neither the option nor the variable existed in the previous build.\n\n- `--review-md <file>`: a new hidden option, left out of the help text, registered next to the existing hidden `--list`, `--output` and `--max-cost` options. It takes a plain file on your computer.\n\n- `CLAUDE_CODE_ULTRAREVIEW_REVIEW_MD_FILE`: a new environment variable, a named setting given to a program from outside it, through which the runner passes the draft along.\n\n- File checks: the file must be UTF-8 text, not blank, a real path rather than a symlink (a shortcut to another file), and under a size limit.\n\n- When it is allowed: only for a pull request reviewed as it was merged (`CLAUDE_CODE_ULTRAREVIEW_PR_AS_MERGED`), with nothing posted to the pull request and no fixes applied. Otherwise nothing is launched and a message explains why.\n\n- Cost notice: it says the file goes to each session \"as a draft REVIEW.md, to be used in place of the repository's own\", and warns that the service limits how many draft reviews one person can start per day.\n\n- Confirm prompt: it shows the start of the draft, with secret-looking text hidden in the preview but still sent. If a secret-looking string cannot be hidden, the run refuses to go ahead.\n\n- What is sent: the full text goes to every review session along with its sha256 fingerprint and first lines, and the scratch copy of the repository writes it as REVIEW.md.\n\n- Report: a new `review_md_sent` field holds the source, sha256 and size in bytes, and the final report says whether every launched review was sent the draft.\n\n- The environment of the processes it starts now also clears `CLAUDECODE`.\n\n**Why**\n\nIn practice, a draft REVIEW.md can stand in for a repository's own for these runs, and you see the start of it and approve it before any review is launched. Note that hidden secret-looking text is still sent, and that draft reviews are limited per person per day.\n\n- Area: Code Review\n- Names: `CLAUDE_CODE_ULTRAREVIEW_REVIEW_MD_FILE`, `\/ultrareview`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}