gitnexus-pr-swarm-review — Claude Code skill: what it does, install
The gitnexus-pr-swarm-review skill splits a pull request review across seven subagents and assembles a production-readiness report. It is built for on-demand PR analysis.
no license 438 installs ★ 48,719 updated 2026-10-25
npx skills add abhigyanpatwari/GitNexus --skill gitnexus-pr-swarm-review -a claude-codeWhat gitnexus-pr-swarm-review does
The skill takes a pull request URL or number and coordinates a GitNexus review. Seven project agents cover separate review lanes: lanes 1–2 start first, lanes 3–6 run concurrently afterward, and lane 7 examines the draft at the end.
The coordinator follows pr-swarm-review/orchestration.md, dispatches work with the Agent tool, and combines findings into the required format. The final report is blocked while the synthesis critic lists required corrections. It only investigates and reports, so it does not edit files, create commits, or post the review.
What it helps with
- check a pull request for production readiness
- split review work among seven subagents
- combine findings from separate review lanes
- hold the final report until required fixes are addressed
Example prompts for the agent
- Run
/gitnexus-pr-swarm-review <PR URL or PR number>to review the pull request. - Ask the skill to perform an on-demand PR review with
/gitnexus-pr-swarm-review <PR URL or PR number>. - After making fixes, run
/gitnexus-pr-swarm-review <PR URL or PR number>again and inspect the revised report.
How to install gitnexus-pr-swarm-review
1Skills CLI (Vercel)
npx skills add abhigyanpatwari/GitNexus --skill gitnexus-pr-swarm-review -a claude-code2Manually: put the files in place
~/.claude/skills/gitnexus-pr-swarm-review/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/gitnexus-pr-swarm-review/
1Skills CLI (Vercel)
npx skills add abhigyanpatwari/GitNexus --skill gitnexus-pr-swarm-review -a codex2Manually: put the files in place
.agents/skills/gitnexus-pr-swarm-review/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add abhigyanpatwari/GitNexus --skill gitnexus-pr-swarm-review -a cursor2Manually: put the files in place
.cursor/skills/gitnexus-pr-swarm-review/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install abhigyanpatwari/GitNexus .claude/skills/gitnexus-pr-swarm-review2Manually: put the files in place
.github/skills/gitnexus-pr-swarm-review/SKILL.md1Skills CLI (Vercel)
npx skills add abhigyanpatwari/GitNexus --skill gitnexus-pr-swarm-review -a gemini-cli2Platform CLI
gemini skills install https://github.com/abhigyanpatwari/GitNexus --path .claude/skills/gitnexus-pr-swarm-reviewManually: put the files in place
.devin/skills/gitnexus-pr-swarm-review/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add abhigyanpatwari/GitNexus --skill gitnexus-pr-swarm-review -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about gitnexus-pr-swarm-review
How do I install gitnexus-pr-swarm-review in Claude Code?
Run npx skills add abhigyanpatwari/GitNexus --skill gitnexus-pr-swarm-review -a claude-code, then check ~/.claude/skills/gitnexus-pr-swarm-review/SKILL.md.
What does gitnexus-pr-swarm-review do?
It coordinates seven subagents to inspect a pull request, merge their findings, and validate the draft before producing the final review.
Why can the final review be held back?
Lane 7 is a required gate. If its synthesis critic lists corrections, the coordinator must revise the draft and run that check again.