
Manage Pr
- Updated March 15, 2026
- shawnburke/claude-plugins
manage-pr creates a pull request and shepherds it to completion — monitoring CI, fixing failures, and addressing review comments. A developer uses it to take a change from PR open to merged without babysitting every step.
Key points
- Creates a PR
- Monitors CI
- Fixes failures
- Addresses review comments
Manage Pr by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin marketplace add shawnburke/claude-plugins/plugin install manage-pr@shawnburke-pluginsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Last updated | March 15, 2026 |
|---|---|
| Repository | shawnburke/claude-plugins ↗ |
What it does
Create a PR and shepherd it to completion — monitor CI, fix failures, and address review comments.
README.md
claude-plugins
Claude Code plugins by shawnburke.
Installation
Inside a Claude Code session, add the marketplace:
/plugin marketplace add shawnburke/claude-plugins
Then install a plugin:
/plugin install manage-pr@shawnburke-plugins
Or run /plugin and use the interactive Marketplaces tab to browse and install.
Plugins
manage-pr
Create a PR and shepherd it to completion — monitors CI, fixes failures, and addresses review comments.
What it does
/manage-pr automates the full lifecycle of getting a PR to a mergeable state:
- Creates the PR — commits any pending changes, creates a branch if needed, pushes, and opens a PR via
gh pr create. If a PR already exists for the branch, it uses that one. - Monitors CI — polls check status (default: every 15s). When a check fails, it fetches the logs, diagnoses the root cause, fixes the code, pushes a new commit, and waits for CI again. Gives up after 5 consecutive failures on the same check and asks for help.
- Addresses review comments — once CI is green, checks for unaddressed review comments. For each comment requesting a change, it modifies the code, pushes a fix, and replies to the comment on the PR. For questions or discussion, it replies without code changes. After pushing fixes, it loops back to wait for CI again.
- Completes — when CI is green and all comments are addressed, it prints a summary and stops.
If new comments arrive after completion, just run /manage-pr again.
Usage
/manage-pr # PR against main, default intervals
/manage-pr develop # PR against develop
/manage-pr --ci-interval 30 # poll CI every 30s instead of 15s
/manage-pr --comment-interval 120 # poll comments every 2 minutes
/manage-pr --rebase # rebase onto latest main before pushing
/manage-pr develop --rebase --ci-interval 10 # combine options
Arguments
| Argument | Default | Description |
|---|---|---|
base-branch |
main (or master) |
Target branch for the PR |
--ci-interval SECONDS |
15 |
How often to poll CI status |
--comment-interval SECONDS |
60 |
How often to poll for review comments |
--rebase |
off | Rebase onto latest base branch HEAD before pushing |
Requirements
- Claude Code
- GitHub CLI (
gh) installed and authenticated (gh auth login) - A git repository with a GitHub remote
Permissions
On first run, the command warms up tool permissions so you can approve all git and gh access patterns up front. This avoids being prompted for each individual command mid-workflow.
Safety
- Never force-pushes unless
--rebaseis used, in which case uses--force-with-lease - Stops after 5 consecutive CI failures on the same check and asks for help
- Asks the user before acting on unclear or contradictory review comments
- Replies to review comments when addressing them so reviewers can see what changed