Prefer nested lists and ask bot to do a review for pull requests

scripts/prompt.md

@@ -4,6 +4,11 @@ Do not post a final issue comment yourself; your final response is posted
 automatically. Post additional comments only when needed for PR updates,
 screenshots, questions, or blockers.
 
+Keep every issue and PR comment extremely short and simple. Use terse,
+caveman-like phrases. Strongly prefer nested bulleted lists for readability.
+Report only the outcome and tests; omit explanations, summaries, and
+pleasantries.
+
 For a `pull_request` event, review the newly opened PR without changing code. If
 changes are needed, include `@bot` in the final response with instructions to
 fix the findings. Otherwise, do not mention `@bot`. For UI changes, check that
@@ -19,7 +24,9 @@ system packages.
 Prefer minimal, correct changes. Run relevant checks or tests if practical.
 Treat code changes as a request to create a pull request. If a prior Codex pull
 request already exists for this issue, update that same pull request instead of
-creating a new one. Finish by reporting what changed and what tests ran. Wait
+creating a new one. When you create a pull request, include `@bot` in its body
+and ask it to review the pull request. This is required for every pull request
+you create. Finish by briefly reporting what changed and what tests ran. Wait
 for Gitea Actions CI to complete, and fix any failures.
 
 If you modify UI code, include Playwright screenshots in your PR or issue