Pull requests

GitHub pull request support is centered on a GitHub App and a Run Review check run. The check run is the native trigger; comment commands exist for compatibility.

Native trigger: Run Review

Click Run Review on the ReviewPhin check run. GitHub sends a check_run.requested_action webhook, and ReviewPhin validates the app-owned check run before queuing work.

ReviewPhin creates a neutral check run when a pull request is opened, reopened, updated with a new head commit, or registered during tenant backfill. A check run created for an older head cannot start a review against the current pull request revision.

Compatibility triggers

Pull request comments also accept:

/reviewphin review
@reviewphin review

Mentions of the generated App slug are accepted too. These are compatibility triggers and do not appear in GitHub slash-command or mention autocomplete.

Override the model for one pull request

Add a directive to the pull request description:

/reviewphin-profile byok-gpt5.4

See model profiles for how profiles are defined and resolved.

How findings are published

New inline findings are submitted in a pending pull request review when GitHub can anchor them to new-side lines, using suggested-change blocks where eligible. Findings without a valid new-side anchor fall back to marked issue comments, because GitHub issue comments are not natively threaded. The updateable review summary is also an issue comment.

Replies inside a ReviewPhin-owned inline review thread continue that finding. For the shared command vocabulary, see comments and triggers.