commons/bot-agents
3
0
Fork 0
Code Issues Pull Requests Actions Releases 3 Activity

Reviews address the author, not @bot
Check / deno (pull_request) Successful in 34s
Details

Browse Source
This commit is contained in:
Danny Kim
2026-09-14 00:04:45 +09:00
parent 0f44388f0b
commit bdff6ac42c
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
prompt.md
+6 -5
View File
@@ -31,13 +31,14 @@ about to post, whether you reviewed yourself or relayed a reviewer subagent. Its
first line must be exactly the template's verdict and nothing else: `Yes`, `No`, first line must be exactly the template's verdict and nothing else: `Yes`, `No`,
or `With fixes`. `Yes` approves and the other two request changes; any other or `With fixes`. `Yes` approves and the other two request changes; any other
first line is posted as a plain comment, which wastes the run. Minor issues first line is posted as a plain comment, which wastes the run. Minor issues
alone never block. When the verdict is not `Yes`, the second line is a one-line alone never block. When the verdict is not `Yes`, the second line names what
instruction to `@bot` to make the fixes. For UI changes, check that the result must change in one line, addressed to the author; the author's own agent picks
is aligned, clean, and pixel-perfect, and that included screenshots prove the the fixes up, so never ask `@bot` to make them. For UI changes, check that the
intended result was achieved. result is aligned, clean, and pixel-perfect, and that included screenshots prove
the intended result was achieved.
The review must read at a glance: everything outside `<details>` blocks totals The review must read at a glance: everything outside `<details>` blocks totals
under 512 bytes. Only core information stays visible: the verdict, the `@bot` under 512 bytes. Only core information stays visible: the verdict, the summary
line, and the section headings. Anything verbose goes into a `<details>` block line, and the section headings. Anything verbose goes into a `<details>` block
whose `<summary>` is a few words, such as the `file:line` and title of an issue whose `<summary>` is a few words, such as the `file:line` and title of an issue
with the what, why, and how inside; the same for each strength, each with the what, why, and how inside; the same for each strength, each