Commands

Post a top-level comment in the pull request's Conversation tab to ask Angada for a review or help.

See the command flow from your perspective

flowchart TD
  A["Open the pull request Conversation tab"] --> B["Post a top-level @angada-ai comment"]
  B --> C{"Are you on the workspace roster or the personal installation owner?"}
  C -- No --> D["Angada reacts with 😕; no public reply"]
  C -- Yes --> E{"Which command did you post?"}
  E -- help or question mark --> F["Angada replies with available commands"]
  E -- Unknown or planned command --> G["Angada reacts with 😕 and points you to help"]
  E -- review or bare mention --> H{"Can Angada review this pull request head?"}
  H -- No --> I["Angada explains what is blocking the review"]
  H -- Yes --> J["Angada reacts with 👀 and reviews the current head"]

help, unsupported commands, and unknown commands do not start a review, create a check run, or use review credits. Review requests can be held by permissions, review settings, limits, or the pull request's current state; see Troubleshoot a review for next steps.

Commands that work today

Use the exact handle @angada-ai; @angada belongs to another GitHub account. Angada reads the token immediately after the handle on the same line, so it does not parse a natural-language request. Text after a supported command is ignored. A reply inside an inline review thread does not run a command; post in the pull request's Conversation tab.

Who can use each re-run option

Each path requires a current pull request head that has not already been reviewed. Workspace roles control Angada actions; GitHub permissions control the Re-run action in Checks. See Re-runs and continuity for how these paths differ.

What happens after a mention

When Angada accepts an eligible review request, it reacts with 👀 and starts a full review of the current head. If the request cannot start, Angada gives an eligible commenter the applicable reason. It can name a closed pull request, a review already running or completed for that head, the mention limit, the pull request or Workspace review cap, exhausted credits, no Review Seat for the pull request author, a skipped-author rule, AI Review being turned off, or GitHub permissions awaiting approval.

Only a workspace roster member can use mention commands, with the personal installation owner as an exception. If someone outside those rules mentions Angada, it reacts with 😕 and does not post a public refusal comment. A roster member who uses an unsupported or unknown command gets a 😕 reaction and a reply that points to help. Neither help nor an unsupported or unknown command starts a review, creates a check run, or uses review credits.

Limits and drafts

• Angada accepts at most three mention-triggered review dispatches for a pull request in a rolling 24-hour window.
• Mention requests still follow the shared pull request and workspace review caps, credit limits, and Review Seat rules. See Limits and caps and Review settings.
• Angada does not review the same head twice. If a review for that head is already running or complete, push a new commit before requesting another review.
• A manual mention can review a draft pull request even when automatic draft reviews are off. It records a per-PR override, so later heads of that draft are also eligible for automatic review.

Upcoming commands

These command ideas are planned and are not available yet. Each is intended to make it easier to work through a review directly from the pull request:

The command list may grow over time. For commands available today, post @angada-ai help in the pull request conversation.

Responding to findings

Use the pull request review controls to resolve a finding after fixing it, or dismiss it when it does not apply. Angada carries those outcomes forward when it matches the same finding on a later pull request head. This helps keep follow-up reviews focused; it does not add a command or change how future findings are generated. See Understand a review for how findings and their outcomes appear across pushes.

Troubleshooting commands

To check the GitHub permissions AI Review needs, see GitHub integration.