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

Superpowers review (#2)

Browse Source 
Superpowers review (#2)

Co-authored-by: Danny Kim <temeddix@gmail.com>
Co-committed-by: Danny Kim <temeddix@gmail.com>
This commit was merged in pull request #2.
This commit is contained in:
Danny Kim
2026-09-13 14:30:29 +00:00
committed by temeddix
parent 8c2041bbc5
commit b8d0093ef2
2 changed files with 32 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
prompt.md
+11 -9
View File
@@ -13,15 +13,17 @@ 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, using the
`requesting-code-review` skill from superpowers: run its code reviewer template
against the PR's base and head, and make its complete output your final response
instead of the short comment style above. Check the whole repository against the
code rules at the end of this prompt, not only the diff; a violation is at least
Important even when the diff did not cause it. 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 instructs `@bot` to make the
fixes exactly when it is not `Yes`, and Minor issues alone never block. 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.