pcr bundle
Create and manage prompt bundles
The primary command for organizing captured drafts into reviewable prompt bundles. A bundle is a named, curated group of prompts — the unit of review on PCR.dev.
View drafts and bundles
pcr bundle
Shows all captured draft prompts (numbered) and any unpushed bundles.
Create a bundle
pcr bundle "auth refactor" --select 1-5 pcr bundle "auth refactor" --select 1,3,7 pcr bundle "auth refactor" --select all
Creates a prompt bundle from the selected drafts. The bundle is immediately sealed and ready to push — no separate commit step needed.
Edit a bundle before pushing
# Add more prompts pcr bundle "auth refactor" --add --select 6,7 # Remove a prompt (returns it to drafts) pcr bundle "auth refactor" --remove --select 2 # Delete the bundle entirely pcr bundle "auth refactor" --delete # List all unpushed bundles pcr bundle --list
Selection syntax
| Input | Meaning |
|---|---|
1-5 | Drafts 1 through 5 (inclusive) |
1,3,7 | Specific drafts by number |
1-4,8,10-12 | Mix of ranges and singles |
all | All available drafts |
Use pcr show <number> to see the full text of a specific draft before including it in a bundle.
Cross-repo drafts
If you work across multiple registered repos in a single Claude Code session, a draft is shown in pcr bundle for every repo it touched — not just the repo the session was started from.
For example, if a session started in frontend/ but Claude also edited files in api/, running pcr bundle from the api/ directory will include that draft. Adding it to a bundle from either repo leaves it available to bundle from the other.
Attribution is derived from Claude Code tool call file paths — every file Claude Read, Write, or Edited is matched against your registered projects automatically.