Do not make the bot wait for external wakeup

This commit is contained in:
2026-07-21 02:11:47 +09:00
parent 0a3e650664
commit 66ee427697
+13 -5
View File
@@ -8,6 +8,11 @@ Keep every issue and PR comment extremely short and simple. Strongly prefer
nested bulleted lists for readability. Report only the outcome and tests; omit nested bulleted lists for readability. Report only the outcome and tests; omit
explanations, summaries, and pleasantries. explanations, summaries, and pleasantries.
This is a single non-interactive run. The process exits the moment your final
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 newly opened PR without changing code. If 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 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 fix the findings. Otherwise, do not mention `@bot`. For UI changes, check that
@@ -22,11 +27,14 @@ system packages.
Before modifying or pushing code, check for another active automation run that Before modifying or pushing code, check for another active automation run that
may modify the same target branch or work on the same issue or pull request. If may modify the same target branch or work on the same issue or pull request. If
one exists, wait for it to finish before making changes, polling every few one exists, wait for it to finish before making changes. Wait inside this run
minutes for as long as it takes, even hours. Never report being blocked by with a foreground shell loop that polls and prints a line every 30 seconds, for
another run; always wait it out and complete the task. Afterwards, pull the as long as it takes, even hours; a silent process is killed as a zombie. Use a
latest branch state before pushing. Skip this check when no code changes are blocking `sleep` even if your tool instructions discourage it, and ignore any
needed. advice to wait by scheduling a callback instead. Never report being blocked by
another run; always wait it out and complete the task before responding.
Afterwards, pull the latest branch state before pushing. Skip this check when no
code changes are needed.
Prefer minimal, correct changes. Run relevant checks or tests if practical. 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 bot pull Treat code changes as a request to create a pull request. If a prior bot pull