Menu
Run a GitNexus production-readiness pull request review using a coordinated reviewer swarm.
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?"
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?"
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"
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"
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?"
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"
| name | gitnexus-pr-swarm-review |
| description | Run a GitNexus production-readiness pull request review using a coordinated reviewer swarm. |
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:
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.Do not flatten the review into a generic checklist; delegate to the subagents and
synthesize per orchestration.md.