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

Refine inline comment formatting: no Bug prefix, summary first, limit suggestion sizeBrowse files

Franklin Volcic authored on Dec 17, 2025 parent 2a61cb3 · commit 1ed82e6af086

1 changed file+9 -6compared with 2a61cb3

Mplugins/code-review/commands/code-review.md

Mplugins/code-review/commands/code-review.md+9 -6

		@@ -52,23 +52,26 @@
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, 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
	55	+7. Post summary comment FIRST using `gh pr comment` (if `--comment` argument is provided):
	56	+ - "## Code review" header
	57	+ - Total number of issues found
	58	+ - Brief one-line summary of each issue (no "Bug:" prefix)
	59	+ - Or if no issues: "No issues found. Checked for bugs and CLAUDE.md compliance."
	60	+
58	61	When writing your comment, follow these guidelines:
59	62	a. Keep your output brief
60	63	b. Avoid emojis
61	64	c. Link and cite relevant code, files, and URLs for each issue
62	65	d. When citing CLAUDE.md violations, you MUST quote the exact text from CLAUDE.md that is being violated (e.g., CLAUDE.md says: "Use snake_case for variable names")
63	66
64		-8. Post inline comments for each issue using `mcp__github_inline_comment__create_inline_comment`:
	67	+8. THEN post inline comments for each issue using `mcp__github_inline_comment__create_inline_comment`:
65	68	- `path`: the file path
66	69	- `line` (and `startLine` for ranges): select the buggy lines so the user sees them
67		- - `body`: Brief description of the issue. For small fixes (1-3 lines), include a committable suggestion:
	70	+ - `body`: Brief description of the issue (no "Bug:" prefix). For small fixes (1-3 lines changed), include a committable suggestion:
68	71	```suggestion
69	72	corrected code here
70	73	```
71		- For larger fixes, describe the solution approach instead of providing code.
	74	+ For larger fixes (4+ lines or structural changes), do NOT use suggestion blocks. Instead, describe at a high level how to fix the issue (e.g., "Consider adding a null check before accessing this property" or "This condition should use === instead of =").
72	75
73	76	IMPORTANT: Only post ONE comment per unique issue. Do not post duplicate comments.
74	77