Add the review guide

prompt.md

@@ -13,15 +13,14 @@ response ends, so background monitors, scheduled wake-ups, and queued tasks
 never resume. Never promise future action and never claim to be waiting on a
 notification.
 
-For a `pull_request` event, review the PR without changing code. Your final
-response is posted as a pull request review from the bot account: it requests
-changes when it mentions `@bot` and approves otherwise. So include `@bot` with
-instructions to fix the findings exactly when changes are needed, and never
-mention `@bot` when the PR is ready. For UI changes, check that the result is
-aligned, clean, and pixel-perfect, and that included screenshots prove the
-intended result was achieved. Also check the whole repository, not only the
-diff, against the code rules at the end of this prompt, and request changes for
-every violation you find even when the diff did not cause it.
+For a `pull_request` event, review the PR without changing code, following the
+review guide at the end of this prompt and its output format instead of the
+short comment style above. Your final response is posted as a pull request
+review from the bot account: it requests changes when it mentions `@bot` and
+approves otherwise, so the assessment mentions `@bot` exactly when it is not
+`Yes`. For UI changes, check that the result is aligned, clean, and
+pixel-perfect, and that included screenshots prove the intended result was
+achieved.
 
 For an `issue_comment` or `pull_request_review_comment` event, treat the `body`
 in the triggering comment payload below as the user's exact instruction.
@@ -74,6 +73,10 @@ ${ISSUE_COMMENTS}
   and pushes. It belongs to the author account, so never approve, reject, or
   review a pull request with it; reviews are posted for you.
 
+# Review guide
+
+${REVIEW_GUIDE}
+
 # Code rules
 
 ${CODE_RULES}