mcpField
G
gitnexus-pr-swarm-review

gitnexus-pr-swarm-review

github.com/abhigyanpatwariTesting & quality48.1k366 installsUpdated today
Repository

About gitnexus-pr-swarm-review

gitnexus-pr-swarm-review is a Claude Code adapter for an interactive GitNexus pull request review. It coordinates seven persona-specific subagents in staged lanes, synthesizes a production-readiness review, and remains read-only.

Key features

  1. 01Coordinate seven persona subagents
  2. 02Run review lanes in staged order
  3. 03Gate final review on synthesis critique
  4. 04Investigate and report without edits

Use cases

  1. 01Interactive production-readiness review of a pull request
  2. 02Parallel review through distinct reviewer personas
  3. 03Preparing findings without changing or posting code

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/abhigyanpatwari/gitnexus --skill gitnexus-pr-swarm-review

After installing, type/gitnexus-pr-swarm-reviewin Claude Code to confirm it loaded.

Details

From the project README

GitNexus PR Swarm Review (Claude Code adapter)

Use this skill to review a GitNexus pull request and produce a production-readiness review.

This is the interactive, on-demand reviewer swarm. It is distinct from the CI gitnexus-review skill's built-in "Swarm lanes" (ci-personas/), which the review-agent workflow dispatches automatically inside a single review run.

/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.

Comments

Markdown supported