Skip to main content
Understand how PRFlow moves a request through an established repository while keeping human control, durable progress and independent review. PRFlow is an orchestrated delivery workflow. It turns a GitHub issue into a branch and a progress record, builds a draft pull request, verifies and reviews the change, updates documentation and hands the result to a person. It does not merge.

​
Core Concepts

The PRFlow Lifecycle

The seven stages an issue passes through, and the gates that can stop a run at each one.

Workpads and Resume

The progress comment PRFlow writes on the issue, and which work survives an interruption.

How PRFlow Verifies a Change

What “recorded verification evidence” means, and why an unknown result is never a pass.

The Review System

The reviewers PRFlow runs, the verdict it reports and what drives a rejection.

Security and Trust

What PRFlow can write, who can start a run and where a cloud run reads its rules from.

Human Control

Every approval, permission and merge boundary that stays with people.

​
A Useful Vocabulary

  • Run: One execution of a PRFlow skill against a repository and, for implementation, a GitHub issue.
  • Workpad: The issue comment that records implementation progress, acceptance criteria and durable notes.
  • Checkpoint: A workpad update, or a scoped commit and push, that reduces how much progress an interrupted run has to reconstruct.
  • Verification evidence: The record of which checks a run executed and what each one returned. See How PRFlow Verifies a Change.
  • Review-ready: The workflow finished and recorded its available verification and review evidence. It is not a guarantee of correctness and it is not permission to merge without review.
Claude Code invokes a skill as /prflow:<skill>. Codex invokes the same skill as $prflow:<skill> or selects it from /skills in Codex CLI. See Commands and Arguments.