surshar / claude-code
Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows - all through natural language commands.
Built by Anthropic · github.com/anthropics
Add ability to run /code-review without posting to GitHub PR. When --no-comment is passed, the review is output to the terminal only. This is useful when running locally and users don't want to clutter PRs with automated comments.
| @@ -26,9 +26,12 @@ | ||
| 26 | 26 | |
| 27 | 27 | **Usage:** |
| 28 | 28 | ```bash |
| 29 | -/code-review | |
| 29 | +/code-review [--no-comment] | |
| 30 | 30 | ``` |
| 31 | 31 | |
| 32 | +**Options:** | |
| 33 | +- `--no-comment`: Skip posting the review to GitHub. Output the review to the terminal only. Useful for local review without creating PR comments. | |
| 34 | + | |
| 32 | 35 | **Example workflow:** |
| 33 | 36 | ```bash |
| 34 | 37 | # On a PR branch, run: |
| @@ -39,6 +42,9 @@ | ||
| 39 | 42 | # - Score each issue for confidence |
| 40 | 43 | # - Post comment with issues ≥80 confidence |
| 41 | 44 | # - Skip posting if no high-confidence issues found |
| 45 | + | |
| 46 | +# For local-only review (no GitHub comment): | |
| 47 | +/code-review --no-comment | |
| 42 | 48 | ``` |
| 43 | 49 | |
| 44 | 50 | **Features:** |
| @@ -49,6 +55,7 @@ | ||
| 49 | 55 | - Historical context analysis via git blame |
| 50 | 56 | - Automatic skipping of closed, draft, or already-reviewed PRs |
| 51 | 57 | - Links directly to code with full SHA and line ranges |
| 58 | +- Optional `--no-comment` flag for local-only review without posting to GitHub | |
| 52 | 59 | |
| 53 | 60 | **Review comment format:** |
| 54 | 61 | ```markdown |
| @@ -196,6 +203,7 @@ | ||
| 196 | 203 | - **Iterate on guidelines**: Update CLAUDE.md based on patterns |
| 197 | 204 | - **Review automatically**: Set up as part of PR workflow |
| 198 | 205 | - **Trust the filtering**: Threshold prevents noise |
| 206 | +- **Use `--no-comment` for local development**: Get review feedback without cluttering the PR | |
| 199 | 207 | |
| 200 | 208 | ## Configuration |
| 201 | 209 |
| @@ -5,6 +5,9 @@ | ||
| 5 | 5 | |
| 6 | 6 | Provide a code review for the given pull request. |
| 7 | 7 | |
| 8 | +**Arguments:** | |
| 9 | +- `--no-comment`: Skip posting the review as a PR comment. Instead, output the review to the terminal only. This is useful when running locally and you don't want to post to GitHub. | |
| 10 | + | |
| 8 | 11 | To do this, follow these steps precisely: |
| 9 | 12 | |
| 10 | 13 | 1. Launch a haiku agent to check if any of the following are true: |
| @@ -52,8 +55,11 @@ | ||
| 52 | 55 | |
| 53 | 56 | 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. |
| 54 | 57 | |
| 55 | -7. Finally, comment on the pull request. | |
| 56 | - When writing your comment, follow these guidelines: | |
| 58 | +7. Finally, output the review: | |
| 59 | + - If `--no-comment` was passed as an argument, output the review directly to the terminal (do NOT post to GitHub) | |
| 60 | + - Otherwise, post the review as a comment on the pull request using `gh pr comment` | |
| 61 | + | |
| 62 | + When writing your review, follow these guidelines: | |
| 57 | 63 | a. Keep your output brief |
| 58 | 64 | b. Avoid emojis |
| 59 | 65 | c. Link and cite relevant code, files, and URLs for each issue |