Installation Problems
PRFlow commands do not appear, a preflight tool is missing, Python is too old or the installer preserved a file.
Command Problems
The command is unknown, GitHub operations fail, the command runs on the wrong target or a verification command is denied.
Implementation Problems
An implement run stops before it opens a pull request: a declared dependency, a bug it cannot reproduce, missing acceptance criteria or a branch it cannot adopt.
Review Problems
A review cannot find the pull request, rejects over a documentation line, reports unverified coverage or delivers no verdict.
Configuration Problems
.prflow/config.json is missing or invalid, a setting is ignored, an override does nothing or a change is not yet in effect.Cloud-Run Problems
A comment did not start a run, the actor was declined, model authentication failed, the job is queued or vendoring failed.
Report a Problem
Run/prflow:help first. It checks your PRFlow version, setup and the failing run, tells you whether the cause is your setup or a likely PRFlow bug, and for a likely bug writes a report under .prflow/tmp/help/ holding the version, operating system, command, local or cloud and the smallest error excerpt. For a cloud run it also saves the failed run’s log in that folder, whatever the verdict. Review the report and remove credentials, prompt text and private repository content before you share it.