Gitnexus Pr Swarm Review
- 216 installs
- 45.1k repo stars
- Updated August 4, 2026
- abhigyanpatwari/gitnexus
gitnexus-pr-swarm-review is a Claude Code skill that coordinates a swarm of reviewer subagents to produce a production-readiness pull request review.
About
This skill runs a GitNexus production-readiness pull request review using a coordinated reviewer swarm. It acts as a swarm coordinator that dispatches seven reviewer personas as subagents, runs review lanes in dependency order, and gates the final review behind a synthesis critic whose required-corrections section must be empty before output. A developer invokes it on a PR URL or number to get a structured production-readiness review. It stays read-only and never edits, commits, or posts.
- Runs a coordinated multi-persona reviewer swarm on a pull request
- Produces a production-readiness review with a hard synthesis-critic gate
- Read-only: investigates and reports, never edits, commits, or posts
Gitnexus Pr Swarm Review by the numbers
- 216 all-time installs (skills.sh)
- Ranked #330 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
gitnexus-pr-swarm-review capabilities & compatibility
- Capabilities
- pr review · code review · multi agent orchestration
- Works with
- github
- Use cases
- code review · orchestration
What gitnexus-pr-swarm-review says it does
Run a GitNexus production-readiness pull request review using a coordinated reviewer swarm.
Stay **read-only**: investigate and report; never edit, commit, or post.
Lane 7 is a hard gate.** Do not emit the final review while the synthesis critic's
npx skills add https://github.com/abhigyanpatwari/gitnexus --skill gitnexus-pr-swarm-reviewAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 216 |
|---|---|
| repo stars | ★ 45.1k |
| Last updated | August 4, 2026 |
| Repository | abhigyanpatwari/gitnexus ↗ |
What it does
Review a pull request with a coordinated reviewer swarm and produce a gated production-readiness report without editing or posting.
Who is it for?
Producing a structured, multi-persona production-readiness review of a pull request.
Skip if: Editing code, committing, or posting comments — it is strictly read-only.
When should I use this skill?
You want a coordinated multi-agent review of a pull request before merge.
What you get
A gated production-readiness review synthesized from multiple reviewer personas.
- A production-readiness pull request review
By the numbers
- 7 reviewer personas dispatched as subagents
- Lane 7 synthesis critic is a hard gate
Files
GitNexus PR Swarm Review (Claude Code adapter)
Use this skill to review a GitNexus pull request and produce a production-readiness review.
/gitnexus-pr-swarm-review <PR URL or PR number>You are the swarm coordinator. The full review contract — lanes, dependencies, classifications, output structure, finding format, hidden-Unicode checks, and behavior rules — is the canonical, CLI-neutral spec:
`pr-swarm-review/orchestration.md` — read it now and follow it.
This adapter only pins the Claude Code specifics:
- Run in Swarm mode. Dispatch each lane as its own subagent via the Agent tool. The
seven subagents are the project agents named gitnexus-* (one per persona); each reads its canonical persona under pr-swarm-review/personas/. Run lanes 1–2 first, lanes 3–6 in parallel after, and lane 7 last on the draft.
- Lane 7 is a hard gate. Do not emit the final review while the synthesis critic's
"Required corrections before posting" section is non-empty — revise and re-run it.
- Stay read-only: investigate and report; never edit, commit, or post.
Do not flatten the review into a generic checklist; delegate to the subagents and synthesize per orchestration.md.
Related skills
Improve Codebase ArchitectureSafely deepen clusters of shallow modules into cohesive, testable units while respecting their external dependencies.566k196k
Caveman ReviewGet ultra-compressed, one-line code review comments that cut noise while keeping every actionable fix.270k94.7kCodebase DesignShared vocabulary for designing deep modules: improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable.266k196kCavecrewDelegate coding tasks to specialized subagents that return compressed output, keeping the main context window usable for much longer sessions.220k94.7kCode ReviewReviews a branch or PR diff on two axes at once: conformance to coding standards plus a code-smell baseline, and whether it actually implements the original spec.201k196k
Requesting Code ReviewDispatch a consistent, high-signal code reviewer subagent that catches plan deviations and quality issues before merging or continuing development.183k264kFAQ
How does the swarm review run?
It dispatches seven reviewer personas as subagents, runs lanes in dependency order, and gates the final review behind a synthesis critic whose 'Required corrections before posting' section must be empty.
Will it edit or post the review?
No. It stays read-only, investigating and reporting without editing, committing, or posting.