Comments and triggers

ReviewPhin accepts manual triggers from supported code review platforms. This page is the shared command vocabulary; the platform pages cover platform-specific behavior for merge requests and pull requests.

Trigger cheat sheet

Expand the action you want. Each block is a plain HTML disclosure, so it works without JavaScript.

Review now

@reviewphin review this

Use an @bot mention on GitLab merge requests. GitHub pull request comments also accept the compatibility command /reviewphin review.

Full review (ignore prior context)

@reviewphin full review

Use a full review when you want ReviewPhin to ignore prior incremental context and rescan the code review more broadly. Also accepts full rescan, fresh full review, full review from scratch, and rescan everything.

Follow up on a finding

Reply inside a ReviewPhin-owned discussion to continue that finding. The worker uses the discussion context instead of requiring another top-level trigger.

Can you suggest a more readable variable name here?

Teach a convention

@reviewphin for future reference, prefer functional React components over class components

Also accepts remember, please remember, going forward, in the future, team policy, stable preference, always prefer, and please prefer. Stored in project memory and applied to future reviews.

Pin a model for one review

Add this to the code review description, not a comment:

/reviewphin-profile byok-gpt5.4

Selects a named model profile for every run on that review.

Platform notes

Command	GitLab	GitHub
@reviewphin review this	Native mention trigger	Compatibility trigger (no autocomplete)
/reviewphin review	—	Compatibility trigger (no autocomplete)
Run Review check run	—	Native trigger
Reply in bot discussion	Continues the finding	Continues the finding
/reviewphin-profile <name>	In MR description	In PR description

GitHub’s primary trigger is the Run Review check run action; comment commands are compatibility paths that GitHub does not autocomplete.