From bdff6ac42c94733eb2abfb663da9a528390ee7f4 Mon Sep 17 00:00:00 2001 From: Danny Kim Date: Mon, 14 Sep 2026 00:04:45 +0900 Subject: [PATCH] Reviews address the author, not @bot --- prompt.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/prompt.md b/prompt.md index 780d476..5605b14 100644 --- a/prompt.md +++ b/prompt.md @@ -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`, 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 -alone never block. When the verdict is not `Yes`, the second line is a one-line -instruction to `@bot` to make the fixes. For UI changes, check that the result -is aligned, clean, and pixel-perfect, and that included screenshots prove the -intended result was achieved. +alone never block. When the verdict is not `Yes`, the second line names what +must change in one line, addressed to the author; the author's own agent picks +the fixes up, so never ask `@bot` to make them. For UI changes, check that the +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 `
` 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 `
` block whose `` 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