Install superpowers and use its review skill

action.yml

@@ -20,20 +20,10 @@ inputs:
   bot-token:
     description: API key or token for the selected bot
     required: false
-  model:
-    description: >-
-      Model for the selected bot. Defaults to `claude-sonnet-5` or
-      `gpt-5.6-terra`, the mid tiers, which cover reviews and fixes.
-    required: false
 
 runs:
   using: composite
   steps:
-    # The agent works on the event's commit with full history, as the author.
-    - uses: actions/checkout@v4
-      with:
-        fetch-depth: 0
-        token: ${{ inputs.author-token }}
     # This step assumes this is `node:24-bookworm` container.
     - name: Install dependencies
       shell: bash
@@ -45,7 +35,6 @@ runs:
         ACTION_PATH: ${{ gitea.action_path }}
         BOT_TYPE: ${{ inputs.bot-type }}
         BOT_TOKEN: ${{ inputs.bot-token }}
-        MODEL: ${{ inputs.model }}
         GITEA_API_URL: ${{ gitea.api_url }}
         GITEA_REPOSITORY: ${{ gitea.repository }}
         GITEA_TOKEN: ${{ inputs.author-token }}

prompt.md

@@ -13,39 +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.
 
-The repository is checked out in the working directory at the event's commit,
+For a `pull_request` event, review the PR without changing code, using the
-the head of the pull request when there is one, with full history and the
-author's push credentials. Read the code there, run its checks and tests when
-they bear on the task, and push from there.
-
-For a `pull_request` event, and for a comment on a pull request that asks you to
-review it, 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. Run the project's checks on the head and treat a
+against the PR's base and head, and make its complete output your final response
-failure as at least Important. Check the whole repository against the code rules
+instead of the short comment style above. Check the whole repository against the
-at the end of this prompt, not only the diff; a violation is at least Important
+code rules at the end of this prompt, not only the diff; a violation is at least
-even when the diff did not cause it. Write the complete review, and nothing
+Important even when the diff did not cause it. Your final response is posted as
-else, to the file `${REVIEW_PATH}`: it is posted verbatim as a pull request
+a pull request review from the bot account: it requests changes when it mentions
-review from the bot account, and your final response is not posted at all. The
+`@bot` and approves otherwise, so the assessment instructs `@bot` to make the
-file's first line must be exactly the verdict and nothing else: `Approved` when
+fixes exactly when it is not `Yes`, and Minor issues alone never block. For UI
-the template's answer is yes, `Changes requested` otherwise. The mark in front
+changes, check that the result is aligned, clean, and pixel-perfect, and that
-of it is added when posting, so write the words alone; any other first line is
+included screenshots prove the intended result was achieved.
-posted as a plain comment, which wastes the run. Minor issues alone never block,
-and neither does a finding the author has answered in the comment history below
-as intended or a false alarm, once the code or docs make that clear. When the
-verdict is `Changes requested`, 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 `<details>` blocks totals
-under 512 bytes. Only core information stays visible: the verdict, the summary
-line, and the section headings. Anything verbose goes into a `<details>` block
-whose `<summary>` 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
-recommendation, the reasoning, and any compliance notes. Details blocks are
-top-level, never inside a list item, because Gitea breaks them there.
 
 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.

run.ts

@@ -20,13 +20,6 @@ const EVENT = env("EVENT_NAME");
 const AUTHOR_TOKEN = env("GITEA_TOKEN");
 const REVIEWER_TOKEN = env("REVIEWER_TOKEN");
 const RULES_PATH = "repos/commons/code-rules/raw/README.md";
-// The mid tiers: a run follows a fixed template and the project's checks.
-const DEFAULT_MODELS: Record<string, string> = {
-  claude: "claude-sonnet-5",
-  codex: "gpt-5.6-terra",
-};
-const model = (bot: string): string =>
-  Deno.env.get("MODEL") || DEFAULT_MODELS[bot];
 
 // The reviewer token is withheld so the agent cannot approve as the bot.
 const { REVIEWER_TOKEN: _, ...agentEnv } = Deno.env.toObject();
@@ -59,29 +52,18 @@ async function postComment(body: string): Promise<void> {
   });
 }
 
-// A review is posted whenever the agent wrote one, whether a review request or
+// A pull request event is a review request, so the response becomes a review:
-// a comment asked for it. It comes through a file, because a final chat message
+// changes are requested when the agent asked @bot to fix something, a failed
-// picks up narration while a file's first line is written on purpose. That line
+// run only comments, and anything else approves.
-// is the verdict, matched whole; anything unexpected only comments, never
-// approves. The mark in front is added here, so it is never part of the match.
-const REVIEW_PATH = `${await Deno.makeTempDir()}/review.md`;
-const VERDICTS: Record<string, [event: string, mark: string]> = {
-  Approved: ["APPROVED", "✅"],
-  "Changes requested": ["REQUEST_CHANGES", "🛑"],
-};
-
 async function postResult(body: string): Promise<void> {
-  const review = await Deno.readTextFile(REVIEW_PATH).catch(() => null);
+  if (EVENT !== "pull_request") return postComment(body);
-  if (review === null) {
+  const event = body.includes("@bot")
-    if (EVENT === "pull_request") {
+    ? "REQUEST_CHANGES"
-      throw new Error(`no review was written to ${REVIEW_PATH}`);
+    : body.startsWith("Bot failed:")
-    }
+    ? "COMMENT"
-    return postComment(body);
+    : "APPROVED";
-  }
-  const [verdict, ...rest] = review.split("\n");
-  const [event, mark] = VERDICTS[verdict.trim()] ?? ["COMMENT", "💬"];
   await gitea(REVIEWER_TOKEN, `repos/${REPO}/pulls/${INDEX}/reviews`, {
-    body: stripAnsi([`${mark} ${verdict.trim()}`, ...rest].join("\n")),
+    body: stripAnsi(body),
     event,
   });
 }
@@ -127,7 +109,6 @@ async function renderPrompt(): Promise<string> {
     GITEA_API_URL: API,
     GITEA_REPOSITORY: REPO,
     ISSUE_INDEX: INDEX,
-    REVIEW_PATH,
   };
   const template = await Deno.readTextFile(
     new URL("prompt.md", import.meta.url),
@@ -141,9 +122,10 @@ async function renderPrompt(): Promise<string> {
 async function runClaude(prompt: string): Promise<string> {
   const token = Deno.env.get("BOT_TOKEN");
   if (!token) {
-    throw new Error(
+    await postComment(
       "Run `claude setup-token` locally and set the `bot-token` action input.",
     );
+    Deno.exit(1);
   }
   await installSuperpowers("claude");
   const claude = new Deno.Command("claude", {
@@ -151,7 +133,7 @@ async function runClaude(prompt: string): Promise<string> {
       "--print",
       "--dangerously-skip-permissions",
       "--model",
-      model("claude"),
+      "claude-fable-5",
       "--output-format",
       "stream-json",
       "--verbose",
@@ -162,7 +144,7 @@ async function runClaude(prompt: string): Promise<string> {
     clearEnv: true,
     stdout: "piped",
   }).spawn();
-  let result: { result?: string; subtype: string } | undefined;
+  let result = "Bot failed: no result";
   // Print events as they stream so the runner does not kill the job as a zombie.
   const lines = claude.stdout
     .pipeThrough(new TextDecoderStream())
@@ -174,13 +156,12 @@ async function runClaude(prompt: string): Promise<string> {
       const text = part.thinking ?? part.text ?? part.name;
       if (text) console.log(text);
     }
-    if (event.type === "result") result = event;
+    if (event.type === "result") {
+      result = event.result ?? `Bot failed: ${event.subtype}`;
+    }
   }
   await claude.status;
-  if (result?.result === undefined) {
+  return result;
-    throw new Error(`claude ended with ${result?.subtype ?? "no result"}`);
-  }
-  return result.result;
 }
 
 // Posts the device code so a human can finish the login on the persisted home.
@@ -216,7 +197,7 @@ async function runCodex(prompt: string): Promise<string> {
     args: [
       "exec",
       "--model",
-      model("codex"),
+      "gpt-5.5",
       "--dangerously-bypass-approvals-and-sandbox",
       "--output-last-message",
       file,
@@ -231,14 +212,9 @@ async function runCodex(prompt: string): Promise<string> {
   return await Deno.readTextFile(file);
 }
 
-try {
+await configureGitAuthor();
-  await configureGitAuthor();
+const prompt = await renderPrompt();
-  const prompt = await renderPrompt();
+const result = env("BOT_TYPE") === "claude"
-  const result = env("BOT_TYPE") === "claude"
+  ? await runClaude(prompt)
-    ? await runClaude(prompt)
+  : await runCodex(prompt);
-    : await runCodex(prompt);
+await postResult(result);
-  await postResult(result);
-} catch (error) {
-  await postComment(`Bot failed: ${error}`);
-  throw error;
-}