File tree Expand file tree Collapse file tree
.github/actions/pr-review/prompts Expand file tree Collapse file tree Original file line number Diff line number Diff line change @@ -89,12 +89,25 @@ Do not delete existing summary comments before the new review has been posted.
8989Use this template for the summary body. The heading must be exactly the ` summary_heading `
9090value from ` .github/pr-context.json ` .
9191
92+ Always include a short review summary before the issue sections. Use 1-3 sentences.
93+ For incremental reviews, explicitly say what the new commits changed and whether prior
94+ bot feedback appears addressed. Use ` existing_findings ` , ` comments ` , and
95+ ` .github/resolved-threads.json ` as context, but verify against the current diff before
96+ claiming something was fixed. If there were no prior findings and no new findings, say
97+ what changed and that no new issues were found. Do not leave the summary as only counts
98+ plus "None found" sections.
99+
92100```
93101<summary_heading> <PR title>
94102
95103**Blocking Issues: N** | **Suggestions: M** | **Threads Resolved: R**
96104_Review mode: incremental since `<last_reviewed_sha short>`_ (or _Review mode: full_)
97105
106+ ### Review Summary
107+ <1-3 sentences describing what was reviewed. In incremental mode, include addressed
108+ prior feedback when applicable, for example "The previous pagination suggestion is now
109+ addressed by passing the page token through the client call. No new issues found.">
110+
98111### Security Issues
99112<one-liner per finding with file:line, or "None found.">
100113
You can’t perform that action at this time.
0 commit comments