gitnexus-pr-swarm-review
Run a GitNexus production-readiness pull request review using a coordinated reviewer swarm.
- Installs
- 357
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/abhigyanpatwari/gitnexus --skill gitnexus-pr-swarm-review- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads gitnexus-pr-swarm-review automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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-reviewskill'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 underpr-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.
FAQ
What does the gitnexus-pr-swarm-review skill do?
Run a GitNexus production-readiness pull request review using a coordinated reviewer swarm.
How do I install gitnexus-pr-swarm-review?
Run npx skills add https://github.com/abhigyanpatwari/gitnexus --skill gitnexus-pr-swarm-review in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/gitnexus-pr-swarm-review/ (personal) or .claude/skills/gitnexus-pr-swarm-review/ (project).
Which AI agents can use gitnexus-pr-swarm-review?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is gitnexus-pr-swarm-review safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains gitnexus-pr-swarm-review?
It is published by abhigyanpatwari in abhigyanpatwari/gitnexus. It has 357 recorded installs.
More from abhigyanpatwari/gitnexus
gitnexus-impact-analysis
abhigyanpatwari/gitnexus
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
gitnexus-exploring
abhigyanpatwari/gitnexus
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"
gitnexus-refactoring
abhigyanpatwari/gitnexus
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"
gitnexus-debugging
abhigyanpatwari/gitnexus
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"
gitnexus-cli
abhigyanpatwari/gitnexus
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"
gitnexus-guide
abhigyanpatwari/gitnexus
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?"
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.