You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Use `add_pr_review_comment` tool for each issue found
149
157
- ONLY comment on lines that are marked as added (+) or modified in the diff
150
158
- Never comment on unchanged context lines or pre-existing code
159
+
- **For repetitive issues**: When the same issue appears on many lines (e.g., missing type hints, consistent style violations), leave a representative comment or group similar issues rather than flagging every instance. This avoids overwhelming PR authors with repetitive feedback.
160
+
- Prefer GitHub suggestion code blocks for simple fixes (typos, imports, formatting) using ```suggestion format so maintainers can apply with one click.
161
+
- Keep indentation: In ```suggestion blocks, copy the original leading spaces/tabs exactly (only change them if that's the actual fix). Avoid extra blank lines and include only the lines you intend to modify.
151
162
- Comment parameters:
152
163
- Single-line: Set `subject_type` to `LINE`, specify `line`
153
164
- Multi-line: Set `subject_type` to `LINE`, specify both `start_line` and `line`
154
165
- Comment format:
155
-
- Use triple backticks (```) for code examples with an appropriate language identifier
156
-
- Be specific about the violation and suggest fixes
166
+
- Use ```suggestion blocks for direct fixes (preferred when possible) or triple backticks (```) for code examples
167
+
- Be specific about the violation and why the change is needed
157
168
- For typos, clearly indicate the correct spelling (e.g., "Typo: 'varabel' should be 'variable'")
169
+
- For grouped issues, mention how many instances were found (e.g., "This function and 3 others are missing type hints")
158
170
- Include `🤖 Generated by Codex` at the end of each comment
0 commit comments