The Problem PRFlow Solves
Coding agents are impressive on a fresh repository and disappointing on a real ticket. Point one at a change in a large production codebase and it usually comes back with part of the work: code that ignores an existing pattern, no tests, documentation left stale and acceptance criteria that were never checked. The agent saved you an hour of typing and cost you two hours of review and cleanup. The bottleneck moved. Writing code got cheap. Everything around it — planning against architecture that already exists, verifying the change, reviewing it seriously, keeping documentation true — did not. That is the work PRFlow does.What You Actually Get
How It Works
Three commands cover the common path.1
Describe the work
/prflow:spec turns a rough idea into a GitHub issue. It reads your repository first, asks the questions it genuinely cannot answer and creates nothing until you approve the exact draft.2
Let PRFlow build it
/prflow:implement 123 creates a branch, plans the change against your existing code, implements it, runs your tests, reviews the diff, fixes what the review found, updates the documentation and opens a pull request. It writes its progress to a comment on the issue as it goes, so you can watch or walk away.3
Review and merge
You read the pull request. PRFlow never merges it. Your branch protection and your normal approval process are untouched.
What Makes the Review Trustworthy
Any single pass from a language model is variable. PRFlow is built around not trusting one.Independent reviewers
Several reviewers with different jobs look at the same change without seeing each other’s conclusions. When more than one raises the same defect, that agreement counts for something.
Verification before opinion
PRFlow builds a checklist of the specific claims a change makes and checks them against the code. A check that fails, or that cannot be settled, blocks a clean approval.
A review of the review
Before an approval stands, a separate pass re-examines the change without the first review’s conclusions, looking for what it missed.
It improves itself
A weekly retrospective reads PRFlow’s own track record and proposes the smallest change that would prevent a repeating mistake. A person approves or rejects each one.
What PRFlow Does Not Do
Honesty here is worth more than a stronger claim.- It does not merge. PRFlow prepares a pull request. Every merge decision stays with a person and with your repository’s protections.
- A clean review is evidence, not proof. The extra review passes narrow the chance of a bad change getting through. They never close it. Reviewers can share the same blind spot, and a test can encode the same wrong assumption as the code it covers.
- It does not invent your requirements. If an issue leaves a decision open, PRFlow stops and asks rather than guessing. A run can end Blocked, which is a result, not a failure.
- It does not run without permission. Locally it uses your session’s tools and permission prompts. In the cloud it runs only when an authorized person asks it to.
Start Here
Quickstart
Install PRFlow and get your first pull request on one page.
Getting Started
Requirements, installation, repository setup and a guided first run.
Workflows
Every command, what it changes and when to reach for it.
How PRFlow Works
The lifecycle, the review system, verification and the security boundaries.