This repository was archived by the owner on Mar 6, 2024. It is now read-only.
File tree Expand file tree Collapse file tree 3 files changed +3085
-1385
lines changed Expand file tree Collapse file tree 3 files changed +3085
-1385
lines changed Original file line number Diff line number Diff line change @@ -124,9 +124,10 @@ inputs:
124
124
and is aware of their implications on the entire system. Instead of
125
125
making generic comments about potential impacts on the system, focus
126
126
on providing specific, objective insights based on the code itself.
127
- Do not question the developer's intention behind the changes or caution
127
+ - Do not question the developer's intention behind the changes or caution
128
128
them to ensure that their modifications do not introduce compatibility
129
- issue with other dependencies.
129
+ issues with other dependencies.
130
+ - Never ask the developer to review the changes.
130
131
summarize :
131
132
required : false
132
133
description : ' The prompt for final summarization response'
Original file line number Diff line number Diff line change @@ -162,13 +162,12 @@ hunk is of the format \`<line_number><colon><whitespace>\`.
162
162
- Replacement suggestions should be complete, correctly formatted and without
163
163
the line number annotations. Each suggestion must be provided as a separate
164
164
review section with relevant line number ranges.
165
- - If needed, suggest new code snippets using the correct language identifier in the
166
- fenced code blocks. These snippets may be added to a different file
165
+ - If needed, suggest new code snippets using the correct language identifier
166
+ in the fenced code blocks. These snippets may be added to a different file
167
167
(e.g. test cases), or within the same file at locations outside the provided
168
168
hunks. Multiple new code snippets are allowed within a single review section.
169
- - If there are no substantive issues detected at a line range and/or the
170
- implementation looks good, you must respond with the comment "LGTM!" and
171
- nothing else for the respective line range in a review section.
169
+ - IMPORTANT: If there are no issues found on a line range, you must only
170
+ respond with the text \`LGTM!\` for that line range in the review section.
172
171
- Reflect on your comments and line number ranges before sending the final
173
172
response to ensure accuracy of line number ranges and replacement snippets.
174
173
You can’t perform that action at this time.
0 commit comments