Skip to main content
Decide where PRFlow does the work: inside your own supported coding-client session, or inside GitHub Actions after an authorized comment. Both modes run the same workflows. They differ in who starts a run, which credentials it uses and how you approve what it does.

​
Compare the Two Modes

Local runs inherit tools, authentication and permission prompts from your coding-client session. They need no GitHub Actions workflow and no repository secret. Cloud runs use committed workflow files, explicit GitHub permissions, repository secrets and a declared setup process. They need more maintenance than the local path.
Claude Code uses /prflow:<skill>. Codex CLI and Codex in the ChatGPT desktop app use $prflow:<skill>; Codex CLI also provides a /skills picker. See Commands and Arguments.

​
What Each Mode Supports

A local install exposes every public PRFlow workflow, including the ones that never run in the cloud: issue authoring, repository initialization, the documentation family and the weekly retrospective. A fresh cloud install ships two workflow files and answers four comment commands: Automatic pull-request-triggered review is not part of a fresh install. If you want a review requested without anyone typing a comment, see Request a Review Automatically on Green CI.
No PRFlow run merges a pull request. Every mode ends with a branch, a pull request, a workpad or a review for a person to read and act on.

​
Start Here

Local Runs

Run PRFlow from a Claude Code or Codex session in your own checkout.

Cloud Runs

Let authorized collaborators start PRFlow from a GitHub comment.

Commands and Arguments

The command syntax, the arguments each workflow accepts and which ones are local-only.

Cloud Triggers

The exact comment format, the surface each command works on and who may fire it.
Begin locally. Add cloud automation once you understand the workflows, the verification commands and the permission scopes they need.