Skip to main content
Run PRFlow directly from Claude Code or Codex. A local run is the fastest way to start, and it needs no GitHub Actions workflow and no repository secret.

​
Run Your First Local Command

1

Open Your Coding Client Inside the Repository

Start the session from anywhere inside the target Git checkout.
2

Enter a Namespaced Command

Claude Code uses /prflow:. Codex uses $prflow: or its /skills picker.
3

Answer the Permission Prompts

Your coding client asks before it edits files, runs a command or calls gh. Approve only what the workflow needs. See Local Permissions.
4

Watch the Run Report Its Progress

An implementation run leaves three things behind:
  • A workpad comment on issue 123, which it keeps updated as it works.
  • A feature branch named after the issue, such as issue-123-add-retry-to-webhook-client.
  • A pull request that links back to the issue.
The workpad’s Status line carries a glyph: 🚀 while the run is still working, then 🎉 Complete, 👎 Blocked, 💥 Failed or 🛑 Cancelled.
🎉 Complete means PRFlow finished its own lifecycle. It does not mean the pull request was merged, and it is not a guarantee that the change is correct. Read the review and the diff before you merge.

​
What a Local Run Uses

  • The repository and Git root discovered from the current directory.
  • Your authenticated GitHub CLI identity.
  • The tests, linters and development tools already installed on the machine.
  • Your coding client’s permission system and your answers to it.
  • Built-in configuration defaults, plus .prflow/config.json overrides when the file is present.
Repository initialization with /prflow:init is recommended so you can customize behavior, but a local run works without it.

​
When to Run Locally

Interactive Decisions

Answer clarification questions while the work is still in progress.

Tight Permission Control

Approve each tool request as it happens instead of granting a standing allowlist.

Local-Only Workflows

Create issues, initialize configuration, update documentation and run the weekly retrospective. None of these has a cloud trigger.

A Trusted Environment

Use services, credentials and development tools that are already set up on your workstation.

​
Next Steps