Skip to main content
Use the right skill syntax and arguments when you run PRFlow from Claude Code or Codex.

​
Choose Your Client’s Syntax

The skill name stays prflow:<skill>. The client decides how you select it.
Enter the skill as a slash command:
Expected result: Claude Code’s completion menu offers the matching PRFlow skill as you enter /prflow:.
Codex can also select a skill implicitly. For example, Use PRFlow to implement GitHub issue 123 matches the installed prflow:implement skill without an explicit mention.
Always include the prflow namespace when you select a skill explicitly. Names such as review and init can collide with built-in client commands and start different behavior.

​
Commands and Their Arguments

Arguments follow the skill name, separated by spaces. Square brackets below mean the argument is optional. The narrower documentation commands docs-sync-internal, docs-sync-external, docs-bootstrap-internal, docs-bootstrap-external and docs-release-notes take no arguments either. See Workflow Guides for what each one produces.
  • A bare number is a pull-request or issue number. In prflow:review and prflow:review-and-fix, only a bare number binds the pull-request number. A number that follows --issue is never read as the pull-request number.
  • Omit the number to work on the current branch. prflow:review, prflow:review-and-fix and prflow:pr-description fall back to the branch you have checked out, compared against the configured base branch.
  • --issue N names the issue whose acceptance criteria the review reads. Use it when the pull request does not already point at the right issue.
  • --push-each-iteration pushes each completed fix cycle, and the final loop state, to the feature branch. Without it a local fix run commits but never pushes, so the fixes stay on your machine.
  • prflow:implement needs an issue number. It reads that issue’s body as the specification.

​
Which Commands Run Only Locally

A fresh cloud installation answers four comment commands. Everything else in the table above is local-only.

Available Locally and in the Cloud

implement, review, review-and-fix and pr-description.

Local Only

spec (alias create-issue), init, the whole docs family and retrospective-weekly.
Two differences matter when you move between the two:
  • A cloud comment command ignores a trailing number. /prflow:review, /prflow:review-and-fix and /prflow:pr-description always act on the thread they were posted on. Locally, a bare number selects a different pull request.
  • /prflow:implement in the cloud runs only from a comment on an issue. A comment on a pull request never starts one.
See Cloud Triggers for the full comment rules.

​
Use the Current Namespace

Use the prflow: namespace for local skills: /prflow: in Claude Code and $prflow: in Codex. GitHub comment triggers continue to use /prflow:. The older /devflow: spelling is still accepted as a compatibility alias for GitHub comment triggers, where it is normalized to the current form. Do not use it in new documentation, scripts or automation.