Skip to main content
PRFlow is the new name for the DevFlow plugin. Update the plugin once, then migrate each existing repository once. The marketplace keeps its original devflow-marketplace name, so do not remove or rename it. If you are installing for the first time, follow Installation instead. Nothing on this page applies to you.

​
Update the Plugin

1

Refresh the Marketplace

2

Install PRFlow

3

Start a New Session

Start a new Claude Code session so the renamed skills load. The interactive /plugin manager offers the same marketplace and install actions if you prefer a menu.
The /devflow:* skill names do not survive the rename in your editor. Use /prflow:* for every local PRFlow skill from now on.
Claude Code’s CLI and its VS Code extension share plugin configuration, so updating in one updates the other. If PRFlow does not appear in VS Code, run the two commands above in VS Code’s integrated terminal and restart Claude Code.

​
Migrate Each Repository

Run this once in every repository that was configured before the rename, including repositories that use GitHub Actions:
Initialization performs the rename first, before it scaffolds anything. It changes these five things:
  • Moves .devflow/ to .prflow/ and updates the vendored plugin path.
  • Renames the supported top-level configuration keys.
  • Updates workflow contents that name the old state directory, vendored path or configuration keys.
  • Updates the repository’s local marketplace reference.
  • Updates the plugin name and version pin.
These changes are applied together or not at all. If any precondition fails, the migration changes nothing and the repository stays byte-for-byte as it was. Follow the reported fix rather than moving files or rewriting workflow paths by hand — a half-migrated repository fails silently instead of loudly.
After the rename attempt, initialization continues with its normal setup and may change other files. Review the final diff either way, including when the rename was refused.

​
Messages You May See

​
After a Successful Migration

1

Read the Full Diff

Check git status and every changed file.
2

Confirm Your Settings Survived

Your configuration values, tuned arrays and custom workflow content should all still be there.
3

Commit Through Your Normal Process

The migration is an ordinary commit and should get an ordinary review.
4

Merge Before Expecting Cloud Runs to Change

GitHub Actions uses the new paths and configuration keys only once the migration reaches your default branch.

​
Optional Product-Name Sweep

After the rename succeeds, /prflow:init may offer to update remaining DevFlow product-name mentions in your own files. This step is optional and is separate from the migration.
Privacy note. The sweep reads tracked, untracked and ignored files, which may hold secrets or private data, and their contents may enter the model’s context. Declining the sweep does not affect the migration, which is already complete.

​
Cloud Repositories

If your repository uses the cloud tier, also review:
  • Any workflow file the migration reports as rewritten.
  • Any warning about a retained workflow the PRFlow installer does not maintain.
  • The migrated workflows.prflow and workflows.prflow-review configuration toggles.
  • The version pin and vendored path, if you use the committed-vendor installation mode.
Existing automation may still post /devflow:implement or /devflow:review comments. Those keep working. Use /prflow:implement and /prflow:review in new comments.

​
Names That Intentionally Stay the Same

Do not run a repository-wide search and replace. Several names keep the DevFlow spelling on purpose, and renaming one of them removes a setting rather than moving it — usually without any error.

​
Verify the Migration

The migration is complete when all of the following are true:
  • Claude Code lists prflow as the installed plugin.
  • /prflow:init is available in a new session.
  • The repository contains .prflow/ and no .devflow/ directory remains.
  • The diff holds the expected moves and rewrites, with your custom values intact.
  • Cloud workflow checks pass after the migration reaches the default branch.