Skip to main content
Pick the smallest PRFlow workflow that produces the outcome you need with the least edit authority. PRFlow commands are Claude Code skills. You run them as /prflow:<skill> in Claude Code, and you run four of them by leaving a comment on a GitHub issue or pull request. See Local Runs and Cloud Runs for the difference. A map of PRFlow skills grouped by outcome. The core delivery skills are prflow:spec, prflow:implement, prflow:review and prflow:review-and-fix. Supporting skills are prflow:pr-description, prflow:docs and prflow:retrospective-weekly.

​
The Delivery Path

These four workflows carry a piece of work from an idea to a pull request a human can merge.

Create an Issue

Turn a rough idea or bug report into one approved GitHub issue. Creates nothing until you approve the final draft.

Implement an Issue

Turn an open issue into a pull request. Creates a branch, commits code and docs, pushes and opens a pull request.

Review

Assess a pull request or branch and return a verdict. Never edits the reviewed tree.

Review and Fix

Assess the same way, then correct what it finds. Commits to the active branch.

​
Supporting Workflows

Pull Request Description

Write or refresh a pull request body from the current branch.

Documentation

Keep developer docs, public docs and release notes in step with the code.

Weekly Retrospective

Learn from recently merged pull requests and file the findings for human triage.

​
Choose a Workflow

Read down the “Your goal” column until you find your case.
review and review-and-fix share the same review engine and produce the same findings. The difference is authority: review reports, review-and-fix edits. Use review-and-fix only when you want PRFlow to change your branch.

​
What No Workflow Does

No PRFlow workflow merges a pull request, and none of them approves its own work. Merge stays with your reviewers and your branch protection rules. See Human Control.