Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Agent skill for pr-manager - invoke with $agent-pr-manager
.claude/skills/agent-pr-manager/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | — | — |
| case-08 | ✗→✓ | ▲ Improved | — | — |
| case-02 | ✗→✗ | = Same ✗ | — | — |
| case-03 | ✗→✗ | = Same ✗ | — | — |
| case-11 | ✗→✗ | = Same ✗ | — | — |
Comprehensive pull request management with swarm coordination for automated reviews, testing, and merge workflows.
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" }
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" } ] }
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" } }
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_spawn { type: "tester", name: "QA Engineer" } mcp__claude-flow__agent_spawn { type: "coordinator", name: "Merge Coordinator" } // Create and manage PR using gh CLI Bash("gh pr create --repo :owner/:repo --title '...' --head '...' --base 'main'") Bash("gh pr view 54 --repo :owner/:repo --json files") Bash("gh pr review 54 --repo :owner/:repo --approve --body '...'") // Execute tests and validation Bash("npm test") Bash("npm run lint") Bash("npm run build") // Track progress TodoWrite { todos: [ { id: "review", content: "Complete code review", status: "completed" }, { id: "test", content: "Run test suite", status: "completed" }, { id: "merge", content: "Merge when ready", status: "pending" } ]}
$github issue-tracker - For project coordination$github branch-manager - For branch strategy$github ci-orchestrator - For CI/CD integration$sparc reviewer - For detailed code analysis$sparc tester - For comprehensive testing| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-02 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-03 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-11 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-01 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-12 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-16 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-04 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-17 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-15 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-10 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-18 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-06 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-09 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-07 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-08 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-22 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-05 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-19 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-13 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-14 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-20 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-21 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted, and 7 counted toward the lift figure. The other 15 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of +9 percentage points is the difference between those two pass rates over the 7 comparable cases. 3 cases got worse with the skill loaded, and they are included in that figure.
The per-case answers from this run were removed by the retention sweep, so the case table below shows the verdicts without the text either arm produced. The counts above were recorded at the time and are unaffected. Answers are now kept for 180 days.
Other measured skills in the registry, with their headline benchmark lift.