Review on request

The review file starts with `Approved` or `Changes requested` instead of `Yes`/`No`/`With fixes`. The match is still the whole trimmed first line; `run.ts` prepends ✅, 🛑, or 💬 when posting, so the mark never takes part in the match.

Verified: `deno fmt`, `deno lint`, `deno check` pass; a scratch run of the matcher maps `Approved` → APPROVED, `Changes requested` → REQUEST_CHANGES, and `Approved, mostly`, `✅ Approved`, `Yes` → COMMENT.
Reviewed-on: #8
Co-authored-by: Danny Kim <temeddix@gmail.com>
Co-committed-by: Danny Kim <temeddix@gmail.com>

.gitea/workflows/check.yml

@@ -0,0 +1,17 @@
+name: Check
+
+on:
+  pull_request:
+    branches: [main]
+
+jobs:
+  deno:
+    runs-on: self-hosted
+    steps:
+      - uses: actions/checkout@v4
+
+      - run: apt-get update && apt-get install -y unzip
+
+      - uses: denoland/setup-deno@v2
+
+      - run: deno fmt --check . && deno lint . && deno check run.ts

action.yml

@@ -1,28 +1,55 @@
-name: Codex Bot
+name: Bot agents
-description: Run Codex CLI for approved Gitea issue/PR automation
+description: Run a coding agent for approved Gitea issue/PR automation
 
 inputs:
-  gitea-token:
+  bot-type:
+    description: Which bot to run, either `codex` or `claude`
     required: true
+  author-token:
+    description: >-
+      Gitea token of the account that commits, pushes, and opens pull requests,
+      with the `read:user`, `write:issue`, and `write:repository` scopes. The
+      agent sees it as `GITEA_TOKEN`.
+    required: true
+  reviewer-token:
+    description: >-
+      Gitea token of the bot account that posts comments and pull request
+      reviews, with the `write:issue` and `write:repository` scopes. Never
+      exposed to the agent, so it must differ from the author.
+    required: true
+  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
-      run: |
+      run: npm install -g @openai/codex @anthropic-ai/claude-code deno
-        apt-get update
+    - name: Run bot
-        apt-get install -y --no-install-recommends gettext-base jq ansifilter
-        npm install -g @openai/codex
-
-    - name: Run Codex Bot
       shell: bash
-      run: bash "${ACTION_PATH}/scripts/run-codex.sh"
+      run: deno run -A "${ACTION_PATH}/run.ts"
       env:
         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.gitea-token }}
+        GITEA_TOKEN: ${{ inputs.author-token }}
-        ISSUE_INDEX: ${{ gitea.event.issue.number }}
+        REVIEWER_TOKEN: ${{ inputs.reviewer-token }}
-        COMMENT_BODY: ${{ gitea.event.comment.body }}
+        EVENT_NAME: ${{ gitea.event_name }}
+        ISSUE_INDEX: ${{ gitea.event.issue.number || gitea.event.pull_request.number }}
+        COMMENT: ${{ toJSON(gitea.event.comment || gitea.event.review) }}

prompt.md

@@ -0,0 +1,103 @@
+You are a coding agent running inside Gitea Actions.
+
+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. Strongly prefer
+nested bulleted lists for readability. Report only the outcome and tests; omit
+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.
+
+The repository is checked out in the working directory at the event's commit,
+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
+failure as at least Important. 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. Write the complete review, and nothing
+else, to the file `${REVIEW_PATH}`: it is posted verbatim as a pull request
+review from the bot account, and your final response is not posted at all. The
+file's first line must be exactly the verdict and nothing else: `Approved` when
+the template's answer is yes, `Changes requested` otherwise. The mark in front
+of it is added when posting, so write the words alone; any other first line is
+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.
+
+Install missing tools yourself when needed, including Rust, uv, Node, Deno, or
+system packages.
+
+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
+one exists, wait for it to finish before making changes. Wait inside this run
+with a foreground shell loop that polls and prints a line every 30 seconds, for
+as long as it takes, even hours; a silent process is killed as a zombie. Use a
+blocking `sleep` even if your tool instructions discourage it, and ignore any
+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 that follow the code rules at the end of this
+prompt. Run relevant checks or tests if practical. Treat code changes as a
+request to create a pull request. If a prior bot pull request already exists for
+this issue, update that same pull request instead of 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
+comments. If you need UI clarification, ask with screenshots when helpful.
+
+# Comment payload
+
+```
+${COMMENT}
+```
+
+# Full issue comment history
+
+```
+${ISSUE_COMMENTS}
+```
+
+# Gitea context
+
+- Event: `${EVENT_NAME}`
+- API URL: `${GITEA_API_URL}`
+- Repository: `${GITEA_REPOSITORY}`
+- Issue index: `${ISSUE_INDEX}`
+- Use the `GITEA_TOKEN` environment variable for authenticated Gitea API calls
+  and pushes. It belongs to the author account, so never approve, reject, or
+  review a pull request with it; reviews are posted for you.
+
+# Code rules
+
+${CODE_RULES}

run.ts

@@ -0,0 +1,244 @@
+// Runs a coding agent for one Gitea issue or pull request event and posts its
+// final response back. The agent works as the author account through
+// GITEA_TOKEN; everything this script posts goes through the reviewer token,
+// so it appears as the bot account.
+import { TextLineStream } from "jsr:@std/streams@1/text-line-stream";
+
+type GiteaUser = { login: string; email: string };
+type GiteaComment = { user: GiteaUser; created_at: string; body: string };
+
+const env = (name: string): string => {
+  const value = Deno.env.get(name);
+  if (value === undefined) throw new Error(`${name} is not set`);
+  return value;
+};
+
+const API = env("GITEA_API_URL");
+const REPO = env("GITEA_REPOSITORY");
+const INDEX = env("ISSUE_INDEX");
+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();
+
+async function gitea(
+  token: string,
+  path: string,
+  body?: unknown,
+): Promise<Response> {
+  const response = await fetch(`${API}/${path}`, {
+    method: body === undefined ? "GET" : "POST",
+    headers: {
+      Authorization: `token ${token}`,
+      "Content-Type": "application/json",
+    },
+    body: body === undefined ? undefined : JSON.stringify(body),
+  });
+  if (!response.ok) {
+    throw new Error(`${path}: ${response.status} ${await response.text()}`);
+  }
+  return response;
+}
+
+const ANSI = new RegExp(`${String.fromCharCode(27)}\\[[0-9;]*[A-Za-z]`, "g");
+const stripAnsi = (text: string): string => text.replace(ANSI, "");
+
+async function postComment(body: string): Promise<void> {
+  await gitea(REVIEWER_TOKEN, `repos/${REPO}/issues/${INDEX}/comments`, {
+    body: stripAnsi(body),
+  });
+}
+
+// A review is posted whenever the agent wrote one, whether a review request or
+// a comment asked for it. It comes through a file, because a final chat message
+// picks up narration while a file's first line is written on purpose. That line
+// 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 (review === null) {
+    if (EVENT === "pull_request") {
+      throw new Error(`no review was written to ${REVIEW_PATH}`);
+    }
+    return postComment(body);
+  }
+  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")),
+    event,
+  });
+}
+
+async function run(command: string, args: string[]): Promise<void> {
+  const { success, code } = await new Deno.Command(command, { args }).output();
+  if (!success) throw new Error(`${command} ${args[0]} exited with ${code}`);
+}
+
+// Commits belong to the same account as the pull request they end up in.
+async function configureGitAuthor(): Promise<void> {
+  const user: GiteaUser = await (await gitea(AUTHOR_TOKEN, "user")).json();
+  for (const [key, value] of [["name", user.login], ["email", user.email]]) {
+    await run("git", ["config", "--global", `user.${key}`, value]);
+  }
+}
+
+// The superpowers plugin gives the agent its skills, including the code review
+// one that the prompt asks for. Both installs are idempotent on the persisted
+// home.
+async function installSuperpowers(bot: string): Promise<void> {
+  const commands = bot === "claude"
+    ? [
+      ["plugin", "marketplace", "add", "obra/superpowers-marketplace"],
+      ["plugin", "install", "-y", "superpowers@superpowers-marketplace"],
+    ]
+    : [["plugin", "add", "superpowers@openai-curated-remote"]];
+  for (const args of commands) await run(bot, args);
+}
+
+async function renderPrompt(): Promise<string> {
+  const comments: GiteaComment[] = await (await gitea(
+    REVIEWER_TOKEN,
+    `repos/${REPO}/issues/${INDEX}/comments?limit=100`,
+  )).json();
+  const values: Record<string, string> = {
+    COMMENT: env("COMMENT"),
+    ISSUE_COMMENTS: comments
+      .map((c) => `## ${c.user.login} at ${c.created_at}\n\n${c.body}\n`)
+      .join("\n"),
+    CODE_RULES: await (await gitea(REVIEWER_TOKEN, RULES_PATH)).text(),
+    EVENT_NAME: EVENT,
+    GITEA_API_URL: API,
+    GITEA_REPOSITORY: REPO,
+    ISSUE_INDEX: INDEX,
+    REVIEW_PATH,
+  };
+  const template = await Deno.readTextFile(
+    new URL("prompt.md", import.meta.url),
+  );
+  return template.replace(
+    /\$\{(\w+)\}/g,
+    (match, name) => values[name] ?? match,
+  );
+}
+
+async function runClaude(prompt: string): Promise<string> {
+  const token = Deno.env.get("BOT_TOKEN");
+  if (!token) {
+    throw new Error(
+      "Run `claude setup-token` locally and set the `bot-token` action input.",
+    );
+  }
+  await installSuperpowers("claude");
+  const claude = new Deno.Command("claude", {
+    args: [
+      "--print",
+      "--dangerously-skip-permissions",
+      "--model",
+      model("claude"),
+      "--output-format",
+      "stream-json",
+      "--verbose",
+      prompt,
+    ],
+    // Claude refuses --dangerously-skip-permissions as root outside a sandbox.
+    env: { ...agentEnv, CLAUDE_CODE_OAUTH_TOKEN: token, IS_SANDBOX: "1" },
+    clearEnv: true,
+    stdout: "piped",
+  }).spawn();
+  let result: { result?: string; subtype: string } | undefined;
+  // Print events as they stream so the runner does not kill the job as a zombie.
+  const lines = claude.stdout
+    .pipeThrough(new TextDecoderStream())
+    .pipeThrough(new TextLineStream());
+  for await (const line of lines) {
+    if (!line) continue;
+    const event = JSON.parse(line);
+    for (const part of event.message?.content ?? []) {
+      const text = part.thinking ?? part.text ?? part.name;
+      if (text) console.log(text);
+    }
+    if (event.type === "result") result = event;
+  }
+  await claude.status;
+  if (result?.result === undefined) {
+    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.
+async function codexDeviceLogin(): Promise<void> {
+  const login = new Deno.Command("codex", {
+    args: ["login", "--device-auth"],
+    stdout: "piped",
+    stderr: "piped",
+  }).spawn();
+  let shown = "";
+  const collect = (stream: ReadableStream<Uint8Array>): Promise<void> =>
+    stream.pipeThrough(new TextDecoderStream()).pipeTo(
+      new WritableStream({ write: (chunk) => void (shown += chunk) }),
+    );
+  const drained = Promise.all([collect(login.stdout), collect(login.stderr)]);
+  await new Promise((resolve) => setTimeout(resolve, 3000));
+  await postComment(shown);
+  await Promise.all([login.status, drained]);
+  const status = await new Deno.Command("codex", { args: ["login", "status"] })
+    .output();
+  await postComment(new TextDecoder().decode(status.stdout));
+}
+
+async function runCodex(prompt: string): Promise<string> {
+  const loggedIn = await new Deno.Command("codex", {
+    args: ["login", "status"],
+  })
+    .output();
+  if (!loggedIn.success) await codexDeviceLogin();
+  await installSuperpowers("codex");
+  const file = await Deno.makeTempFile();
+  const status = await new Deno.Command("codex", {
+    args: [
+      "exec",
+      "--model",
+      model("codex"),
+      "--dangerously-bypass-approvals-and-sandbox",
+      "--output-last-message",
+      file,
+      prompt,
+    ],
+    env: agentEnv,
+    clearEnv: true,
+    stdout: "inherit",
+    stderr: "inherit",
+  }).spawn().status;
+  if (!status.success) throw new Error(`codex exited with ${status.code}`);
+  return await Deno.readTextFile(file);
+}
+
+try {
+  await configureGitAuthor();
+  const prompt = await renderPrompt();
+  const result = env("BOT_TYPE") === "claude"
+    ? await runClaude(prompt)
+    : await runCodex(prompt);
+  await postResult(result);
+} catch (error) {
+  await postComment(`Bot failed: ${error}`);
+  throw error;
+}

scripts/prompt.md

@@ -1,25 +0,0 @@
-You are Codex running inside Gitea Actions.
-
-First read `.codex-bot/context.md`. Treat the triggering comment body below as
-the user's exact instruction.
-
-Install missing tools yourself when needed, including Rust, uv, Node, Deno, or
-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
-for Gitea Actions CI to complete, and fix any failures.
-
-# Comment body
-
-```
-${COMMENT_BODY}
-```
-
-# Full issue comment history
-
-```
-${ISSUE_COMMENTS}
-```

scripts/run-codex.sh

@@ -1,43 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-git config --global user.name bot
-git config --global user.email noreply@capsulizers.com
-
-COMMENT_FILE="$(mktemp)"
-
-post_comment() {
-  COMMENT_JSON="$(jq -n --rawfile body "${COMMENT_FILE}" '{body: $body}')"
-  curl --fail-with-body --silent --show-error \
-    -X POST \
-    -H "Authorization: token ${GITEA_TOKEN}" \
-    -H "Content-Type: application/json" \
-    --data "${COMMENT_JSON}" \
-    "${GITEA_API_URL}/repos/${GITEA_REPOSITORY}/issues/${ISSUE_INDEX}/comments"
-}
-
-if ! codex login status > /dev/null 2>&1; then
-  codex login --device-auth 2>&1 | ansifilter > "${COMMENT_FILE}" &
-  LOGIN_PID="${!}"
-  sleep 3
-  post_comment
-  wait "${LOGIN_PID}"
-  codex login status 2>&1 | ansifilter > "${COMMENT_FILE}"
-  post_comment
-fi
-
-export ISSUE_COMMENTS="$(
-  curl --fail-with-body --silent --show-error \
-    -H "Authorization: token ${GITEA_TOKEN}" \
-    "${GITEA_API_URL}/repos/${GITEA_REPOSITORY}/issues/${ISSUE_INDEX}/comments?limit=100" \
-    | jq -r '.[] | "## " + .user.login + " at " + .created_at + "\n\n" + .body + "\n"'
-)"
-
-FINAL_PROMPT="$(envsubst < "${ACTION_PATH}/scripts/prompt.md")"
-
-codex exec \
-  --dangerously-bypass-approvals-and-sandbox \
-  --output-last-message "${COMMENT_FILE}" \
-  "${FINAL_PROMPT}"
-
-post_comment