Skip to content

Add PR summary to code review comments #15725

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pt-anthropic wants to merge 4 commits into
base: main
Choose a base branch
from
+13 −13
Open

Add PR summary to code review comments #15725

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
147f010
Enhance code review summary with PR details and review scope
claude Dec 29, 2025
c3cdd04
Always post summary comment, even when issues are found
claude Dec 29, 2025
0108062
Remove 'Files reviewed' from summary comment
claude Dec 29, 2025
02d7e56
Simplify review section in summary comment
claude Dec 29, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 13 additions & 13 deletions plugins/code-review/commands/code-review.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,12 +52,20 @@ 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. If issues were found, skip to step 8 to post inline comments directly.
7. Post a summary comment using `gh pr comment` (if `--comment` argument is provided) with the following structure:

If NO issues were found, post a summary comment using `gh pr comment` (if `--comment` argument is provided):
"No issues found. Checked for bugs and CLAUDE.md compliance."
```
## Code review

8. Post inline comments for each issue using `mcp__github_inline_comment__create_inline_comment`:
### Summary
[2-3 sentence summary of what the PR does, based on the summary from step 3]

### Review
[If no issues: "No issues found."]
[If issues found: "Found N issue(s). See inline comments below."]
```

8. If issues were found, post inline comments for each issue using `mcp__github_inline_comment__create_inline_comment`:
- `path`: the file path
- `line` (and `startLine` for ranges): select the buggy lines so the user sees them
- `body`: Brief description of the issue (no "Bug:" prefix). For small fixes (up to 5 lines changed), include a committable suggestion:
Expand Down Expand Up @@ -91,15 +99,7 @@ Notes:
- Use gh CLI to interact with GitHub (e.g., fetch pull requests, create comments). Do not use web fetch.
- Create a todo list before starting.
- You must cite and link each issue in inline comments (e.g., if referring to a CLAUDE.md, include a link to it).
- If no issues are found, post a comment with the following format:

---

## Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

---
- Always post a summary comment using the format specified in step 7.

- When linking to code in inline comments, follow the following format precisely, otherwise the Markdown preview won't render correctly: https://github.com/anthropics/claude-code/blob/c21d3c10bc8e898b7ac1a2d745bdc9bc4e423afe/package.json#L10-L15
- Requires full git sha
Expand Down