Review a GitNexus pull request for production readiness with seven coordinated reviewer agents. Combine their findings and have a final critic check the draft, producing a review without editing code or posting results.
Run a GitNexus production-readiness pull request review using a coordinated reviewer swarm.
Review the instructions the agent will receive before you install.
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:
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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Build and maintain a GitNexus code index, a searchable map of code relationships. Use CLI commands to refresh or remove indexes, check their status, list indexed projects, and generate repository documentation with an LLM.
Investigate errors and unexpected behavior by finding related code, following function calls, and checking source files. GitNexus helps trace execution paths, while the diagnosis identifies the repository and reports how current its code index is.
Explore unfamiliar code with GitNexus to understand project structure and execution flows. Find related functions, inspect their callers and callees, and read implementation files to explain how a feature works, with repository and index freshness information.
Find the right GitNexus tools and workflows for exploring code relationships. This reference explains available commands, graph queries, and resources, including how to check which branch an answer describes and whether its index is current.
Assess the impact of code changes with GitNexus by tracing callers, dependencies, and affected execution flows. Check existing changes and report their scope, risk, and uncertainty before editing or committing.
Coordinate a development task from planning through implementation and review. Choose whether to proceed after seeing the plan, then receive a report covering commits, verification results, review findings, and any work left unfinished.