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
Change the default behavior of /code-review to output to the terminal instead of posting a PR comment. Users can use the --comment flag to explicitly post the review as a PR comment when desired. This is more suitable for local development workflows where posting comments to the PR is not always needed.
| @@ -22,23 +22,29 @@ | ||
| 22 | 22 | - **Agent #4**: Analyze git blame/history for context-based issues |
| 23 | 23 | 5. Scores each issue 0-100 for confidence level |
| 24 | 24 | 6. Filters out issues below 80 confidence threshold |
| 25 | -7. Posts review comment with high-confidence issues only | |
| 25 | +7. Outputs review (to terminal by default, or as PR comment with `--comment` flag) | |
| 26 | 26 | |
| 27 | 27 | **Usage:** |
| 28 | 28 | ```bash |
| 29 | -/code-review | |
| 29 | +/code-review [--comment] | |
| 30 | 30 | ``` |
| 31 | 31 | |
| 32 | +**Options:** | |
| 33 | +- `--comment`: Post the review as a comment on the pull request (default: outputs to terminal only) | |
| 34 | + | |
| 32 | 35 | **Example workflow:** |
| 33 | 36 | ```bash |
| 34 | -# On a PR branch, run: | |
| 37 | +# On a PR branch, run locally (outputs to terminal): | |
| 35 | 38 | /code-review |
| 36 | 39 | |
| 40 | +# Post review as PR comment: | |
| 41 | +/code-review --comment | |
| 42 | + | |
| 37 | 43 | # Claude will: |
| 38 | 44 | # - Launch 4 review agents in parallel |
| 39 | 45 | # - Score each issue for confidence |
| 40 | -# - Post comment with issues ≥80 confidence | |
| 41 | -# - Skip posting if no high-confidence issues found | |
| 46 | +# - Output issues ≥80 confidence (to terminal or PR depending on flag) | |
| 47 | +# - Skip if no high-confidence issues found | |
| 42 | 48 | ``` |
| 43 | 49 | |
| 44 | 50 | **Features:** |
| @@ -114,17 +120,23 @@ | ||
| 114 | 120 | ### Standard PR review workflow: |
| 115 | 121 | ```bash |
| 116 | 122 | # Create PR with changes |
| 123 | +# Run local review (outputs to terminal) | |
| 117 | 124 | /code-review |
| 118 | 125 | |
| 119 | 126 | # Review the automated feedback |
| 120 | 127 | # Make any necessary fixes |
| 128 | + | |
| 129 | +# Optionally post as PR comment | |
| 130 | +/code-review --comment | |
| 131 | + | |
| 121 | 132 | # Merge when ready |
| 122 | 133 | ``` |
| 123 | 134 | |
| 124 | 135 | ### As part of CI/CD: |
| 125 | 136 | ```bash |
| 126 | 137 | # Trigger on PR creation or update |
| 127 | -# Automatically posts review comments | |
| 138 | +# Use --comment flag to post review comments | |
| 139 | +/code-review --comment | |
| 128 | 140 | # Skip if review already exists |
| 129 | 141 | ``` |
| 130 | 142 |
| @@ -52,7 +52,9 @@ | ||
| 52 | 52 | |
| 53 | 53 | 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 | 54 | |
| 55 | -7. Finally, comment on the pull request. | |
| 55 | +7. Finally, output the review. | |
| 56 | + - If the `--comment` argument is provided, post the review as a comment on the pull request using `gh pr comment` | |
| 57 | + - Otherwise (default), output the review directly to the terminal for local viewing | |
| 56 | 58 | When writing your comment, follow these guidelines: |
| 57 | 59 | a. Keep your output brief |
| 58 | 60 | b. Avoid emojis |