
Agent Pr Manager
Automate pull request reviews, testing gates, conflict handling, and merge workflows with Claude Flow swarm and GitHub MCP tools.
Overview
Agent PR Manager is an agent skill most often used in Ship (also Build) that manages GitHub pull requests with swarm coordination for reviews, testing, and merge workflows.
Install
npx skills add https://github.com/ruvnet/ruflo --skill agent-pr-managerWhat is this skill?
- Swarm-coordinated multi-reviewer PR workflows via claude-flow MCP tools
- Automated conflict resolution and merge strategy guidance
- Pre-hooks: gh auth, git status, open PR probe, and npm test sanity check
- Post-hooks: pr status, branch name, pr checks, and recent commit log
- Integrates github_pr_manage, github_code_review, and github_metrics MCP capabilities
- Pre-task hooks include four checks: gh auth, git status, open PR list, and npm test
- Post-task hooks include four follow-ups: pr status, current branch, pr checks, and last three commits
Adoption & trust: 645 installs on skills.sh; 58.5k GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
Open PRs pile up and you lack a repeatable way to run reviews, tests, conflict handling, and merge checks with your coding agent.
Who is it for?
Indie developers using GitHub CLI and Claude Flow MCP who want agent-driven PR review and merge automation on active branches.
Skip if: Builders not on GitHub, without gh authentication, or who only need local commits with no PR process.
When should I use this skill?
You need comprehensive GitHub pull request management with swarm coordination, automated review, testing integration, and merge workflows (invoke as $agent-pr-manager / pr-manager).
What do I get? / Deliverables
You get orchestrated PR review and merge workflows with pre/post GitHub and test gates plus swarm-backed tracking until the branch is ready to merge.
- Coordinated PR review and agent assignment outcome
- Documented PR checks status and merge readiness
- Conflict-resolution and merge-strategy guidance for the active PR
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Ship is canonical because the skill’s purpose is PR lifecycle management—review, checks, merge—not greenfield coding or growth analytics. Review is the right subphase for multi-reviewer coordination, code review MCP hooks, and merge strategy work on open PRs.
Where it fits
Spawn review agents and run github_code_review on an open PR after npm test passes the pre-hook.
Validate pr checks and merge strategy before shipping a release branch to main.
Track open PRs and swarm status while coordinating multiple tasks tied to GitHub issues.
How it compares
GitHub PR workflow with swarm MCP tools—not a static code-review checklist skill with no gh integration.
Common Questions / FAQ
Who is agent-pr-manager for?
Solo and small-team builders who merge through GitHub PRs and want swarm-coordinated reviews, checks, and merge assistance from their agent.
When should I use agent-pr-manager?
In Ship during code review and pre-merge validation; also in Build when a feature branch is ready for PR creation and automated review passes before you call it done.
Is agent-pr-manager safe to install?
It runs git, gh, tests, and GitHub MCP actions that can modify PR state—review the Security Audits panel on this Prism page and confirm branch and repo scope before enabling hooks.
SKILL.md
READMESKILL.md - Agent Pr Manager
--- name: pr-manager description: Comprehensive pull request management with swarm coordination for automated reviews, testing, and merge workflows type: development color: "#4ECDC4" tools: - Bash - Read - Write - Edit - Glob - Grep - LS - TodoWrite - mcp__claude-flow__swarm_init - mcp__claude-flow__agent_spawn - mcp__claude-flow__task_orchestrate - mcp__claude-flow__swarm_status - mcp__claude-flow__memory_usage - mcp__claude-flow__github_pr_manage - mcp__claude-flow__github_code_review - mcp__claude-flow__github_metrics hooks: pre: - "gh auth status || (echo 'GitHub CLI not authenticated' && exit 1)" - "git status --porcelain" - "gh pr list --state open --limit 1 >$dev$null || echo 'No open PRs'" - "npm test --silent || echo 'Tests may need attention'" post: - "gh pr status || echo 'No active PR in current branch'" - "git branch --show-current" - "gh pr checks || echo 'No PR checks available'" - "git log --oneline -3" --- # GitHub PR Manager ## Purpose Comprehensive pull request management with swarm coordination for automated reviews, testing, and merge workflows. ## Capabilities - **Multi-reviewer coordination** with swarm agents - **Automated conflict resolution** and merge strategies - **Comprehensive testing** integration and validation - **Real-time progress tracking** with GitHub issue coordination - **Intelligent branch management** and synchronization ## Usage Patterns ### 1. Create and Manage PR with Swarm Coordination ```javascript // Initialize review swarm mcp__claude-flow__swarm_init { topology: "mesh", maxAgents: 4 } mcp__claude-flow__agent_spawn { type: "reviewer", name: "Code Quality Reviewer" } mcp__claude-flow__agent_spawn { type: "tester", name: "Testing Agent" } mcp__claude-flow__agent_spawn { type: "coordinator", name: "PR Coordinator" } // Create PR and orchestrate review mcp__github__create_pull_request { owner: "ruvnet", repo: "ruv-FANN", title: "Integration: claude-code-flow and ruv-swarm", head: "integration$claude-code-flow-ruv-swarm", base: "main", body: "Comprehensive integration between packages..." } // Orchestrate review process mcp__claude-flow__task_orchestrate { task: "Complete PR review with testing and validation", strategy: "parallel", priority: "high" } ``` ### 2. Automated Multi-File Review ```javascript // Get PR files and create parallel review tasks mcp__github__get_pull_request_files { owner: "ruvnet", repo: "ruv-FANN", pull_number: 54 } // Create coordinated reviews mcp__github__create_pull_request_review { owner: "ruvnet", repo: "ruv-FANN", pull_number: 54, body: "Automated swarm review with comprehensive analysis", event: "APPROVE", comments: [ { path: "package.json", line: 78, body: "Dependency integration verified" }, { path: "src$index.js", line: 45, body: "Import structure optimized" } ] } ``` ### 3. Merge Coordination with Testing ```javascript // Validate PR status and merge when ready mcp__github__get_pull_request_status { owner: "ruvnet", repo: "ruv-FANN", pull_number: 54 } // Merge with coordination mcp__github__merge_pull_request { owner: "ruvnet", repo: "ruv-FANN", pull_number: 54, merge_method: "squash", commit_title: "feat: Complete claude-code-flow and ruv-swarm integration", commit_message: "Comprehensive integration with swarm coordination" } // Post-merge coordination mcp__claude-flow__memory_usage { action: "store", key: "pr/54$merged", value: { timestamp: Date.now(), status: "success" } } ``` ## Batch Operations Example ### Complete PR Lifecycle in Parallel: ```javascript [Single Message - Complete PR Management]: // Initialize coordination mcp__claude-flow__swarm_init { topology: "hierarchical", maxAgents: 5 } mcp__claude-flow__agent_spawn { type: "reviewer", name: "Senior Reviewer" } mcp__claude-flow__agent_sp