From 26315247e751a2bbb0b1e4d6e6ab679ebb2f706e Mon Sep 17 00:00:00 2001 From: Franklin Volcic Date: Thu, 15 Jan 2026 21:12:50 -0800 Subject: [PATCH 1/2] Minor code review fixes --- plugins/code-review/commands/code-review.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/plugins/code-review/commands/code-review.md b/plugins/code-review/commands/code-review.md index 86c7823c..4d839878 100644 --- a/plugins/code-review/commands/code-review.md +++ b/plugins/code-review/commands/code-review.md @@ -3,10 +3,10 @@ allowed-tools: Bash(gh issue view:*), Bash(gh search:*), Bash(gh issue list:*), description: Code review a pull request --- -Provide a code review for the given pull request. +Provide a code review for the given pull request with ultrathink. **Agent assumptions (applies to all agents and subagents):** -- All tools are functional and will work without error. Do not test tools or make exploratory calls. +- All tools are functional and will work without error. Do not test tools or make exploratory calls. Make sure this is clear to every subagent that is launched. - Only call a tool if it is required to complete the task. Every tool call should have a clear purpose. To do this, follow these steps precisely: @@ -61,10 +61,13 @@ Note: Still review Claude generated PR's. 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." -8. Post inline comments for each issue using `mcp__github_inline_comment__create_inline_comment`. For each comment: +8. Create a list of all comments that you plan on leaving. This is only for you to make sure you are comfortable with the comments. Do not post this list anywhere. + +9. Post inline comments for each issue using `mcp__github_inline_comment__create_inline_comment`. For each comment: - Provide a brief description of the issue - For small, self-contained fixes, include a committable suggestion block - For larger fixes (6+ lines, structural changes, or changes spanning multiple locations), describe the issue and suggested fix without a suggestion block + - Never post a committable suggestion UNLESS committing the suggestion fixes the issue entirely. If follow up steps are required, do not leave a committable suggestion. **IMPORTANT: Only post ONE comment per unique issue. Do not post duplicate comments.** From fd8f3801b931151def2e6f4d00b6aecd29f2fb3e Mon Sep 17 00:00:00 2001 From: Franklin Volcic Date: Thu, 15 Jan 2026 21:29:38 -0800 Subject: [PATCH 2/2] minor update --- plugins/code-review/commands/code-review.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugins/code-review/commands/code-review.md b/plugins/code-review/commands/code-review.md index 4d839878..8fac4231 100644 --- a/plugins/code-review/commands/code-review.md +++ b/plugins/code-review/commands/code-review.md @@ -3,7 +3,7 @@ allowed-tools: Bash(gh issue view:*), Bash(gh search:*), Bash(gh issue list:*), description: Code review a pull request --- -Provide a code review for the given pull request with ultrathink. +Provide a code review for the given pull request. **Agent assumptions (applies to all agents and subagents):** - All tools are functional and will work without error. Do not test tools or make exploratory calls. Make sure this is clear to every subagent that is launched.