# swarm-pr

swarm-pr coordinates agents working on a GitHub pull request, from diff analysis and review to reporting results back to the PR.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 850 repo stars
- Author: ruvnet
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/ruvnet/agentic-flow/tree/HEAD/.claude/agents/github/swarm-pr.md
- Updated: 2026-10-26
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/swarm-pr

## What it does

The subagent uses pull request context, including the diff, to divide review and validation work among agents. It can gather their results and update the PR; its available GitHub tools cover reading and editing pull requests, posting comments, and merging.

Agent types can be assigned from PR labels. A `bug` label maps to `debugger` and `tester`, while `docs` maps to `researcher` and `writer`. swarm-pr also has tools for task coordination and swarm memory. GitHub operations depend on the `mcp__github__*` tools being available; without them, it cannot act on PRs.

## Requirements
- Works with: GitHub

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/agents/swarm-pr.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/swarm-pr.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/swarm-pr.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/ruvnet/agentic-flow/tree/HEAD/.claude/agents/github/swarm-pr.md

## When to use it
- inspect a pull request diff and assess its impact
- split a PR review across specialized agents
- assign agents based on pull request labels
- post review findings to a pull request
- coordinate work across related pull requests

## Example prompts
- Review this pull request diff with multiple agents and organize the checks.
- Choose agents for this PR from its labels and divide the work.
- Post the review findings to the pull request and prepare a merge decision.

## Similar
- [gitnexus-pr-swarm-review](https://affpapa.org/en/nevibecode/skills/gitnexus-pr-swarm-review.md) — skill · 438 installs
- [swarm-pr-feedback](https://affpapa.org/en/nevibecode/skills/swarm-pr-feedback-2.md) — skill · ★ 539 repo stars
- [swarm-pr-subscribe](https://affpapa.org/en/nevibecode/skills/zaxbyhub-swarm-pr-subscribe.md) — skill · ★ 539 repo stars
- [autofix](https://affpapa.org/en/nevibecode/skills/autofix.md) — skill · 12100 installs
- [ce-resolve-pr-feedback](https://affpapa.org/en/nevibecode/skills/ce-resolve-pr-feedback.md) — skill · 3400 installs
- [babysit](https://affpapa.org/en/nevibecode/skills/michael-denyer-babysit.md) — skill · 1100 installs

From the same set: [ruvnet/agentic-flow](https://affpapa.org/en/nevibecode/by/ruvnet/agentic-flow.md) — 76 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
