feat(code-review): Make local-only output the default behavior

Change default to output review to terminal only. Users must now
pass --comment to post to GitHub PR. This is more convenient for
local development where posting to PRs is usually not desired.

CHANGELOG.md

@@ -1,8 +1,20 @@
 # Changelog
 
+## 2.0.69
+
+- Minor bugfixes
+
+## 2.0.68
+
+- Fixed IME (Input Method Editor) support for languages like Chinese, Japanese, and Korean by correctly positioning the composition window at the cursor
+- Fixed a bug where disallowed MCP tools were visible to the model
+- Fixed an issue where steering messages could be lost while a subagent is working
+- Fixed Option+Arrow word navigation treating entire CJK (Chinese, Japanese, Korean) text sequences as a single word instead of navigating by word boundaries
+- Improved plan mode exit UX: show simplified yes/no dialog when exiting with empty or missing plan instead of throwing an error
+- Add support for enterprise managed settings. Contact your Anthropic account team to enable this feature.
+
 ## 2.0.67
 
-- Claude now suggests prompts to speed up your workflow: press Tab to accept or Enter to submit
 - Thinking mode is now enabled by default for Opus 4.5
 - Thinking mode configuration has moved to /config
 - Added search functionality to `/permissions` command with `/` keyboard shortcut for filtering rules by tool name

plugins/code-review/README.md

@@ -26,19 +26,24 @@ Performs automated code review on a pull request using multiple specialized agen
 
 **Usage:**
 ```bash
-/code-review
+/code-review [--comment]
 ```
 
+**Options:**
+- `--comment`: Post the review as a PR comment on GitHub. By default, the review is output to the terminal only.
+
 **Example workflow:**
 ```bash
-# On a PR branch, run:
+# On a PR branch, run (outputs to terminal only):
 /code-review
 
 # Claude will:
 # - Launch 4 review agents in parallel
 # - Score each issue for confidence
-# - Post comment with issues ≥80 confidence
-# - Skip posting if no high-confidence issues found
+# - Output review with issues ≥80 confidence to terminal
+
+# To post review as a GitHub PR comment:
+/code-review --comment
 ```
 
 **Features:**
@@ -49,6 +54,7 @@ Performs automated code review on a pull request using multiple specialized agen
 - Historical context analysis via git blame
 - Automatic skipping of closed, draft, or already-reviewed PRs
 - Links directly to code with full SHA and line ranges
+- Local-only output by default; use `--comment` flag to post to GitHub PR
 
 **Review comment format:**
 ```markdown
@@ -196,6 +202,7 @@ https://github.com/owner/repo/blob/[full-sha]/path/file.ext#L[start]-L[end]
 - **Iterate on guidelines**: Update CLAUDE.md based on patterns
 - **Review automatically**: Set up as part of PR workflow
 - **Trust the filtering**: Threshold prevents noise
+- **Use `--comment` for CI/CD**: Post review to PR when running in automated workflows
 
 ## Configuration
 

plugins/code-review/commands/code-review.md

@@ -5,6 +5,9 @@ description: Code review a pull request
 
 Provide a code review for the given pull request.
 
+**Arguments:**
+- `--comment`: Post the review as a PR comment on GitHub. By default, the review is output to the terminal only.
+
 To do this, follow these steps precisely:
 
 1. Launch a haiku agent to check if any of the following are true:
@@ -52,8 +55,11 @@ Note: Still review Claude generated PR's.
 
 6. Filter out any issues that were not validated in step 5. This step will give us our list of high signal issues for our review.
 
-7. Finally, comment on the pull request.
-   When writing your comment, follow these guidelines:
+7. Finally, output the review:
+   - If `--comment` was passed as an argument, post the review as a comment on the pull request using `gh pr comment`
+   - Otherwise, output the review directly to the terminal (do NOT post to GitHub)
+
+   When writing your review, follow these guidelines:
    a. Keep your output brief
    b. Avoid emojis
    c. Link and cite relevant code, files, and URLs for each issue