abhigyanpatwari/gitnexus

gitnexus-pr-swarm-review

Run a GitNexus production-readiness pull request review using a coordinated reviewer swarm.

Quelltext ansehen

Verwendung

  1. Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
  2. Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
  3. Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/abhigyanpatwari/gitnexus --skill gitnexus-pr-swarm-review

Vor dem Start

  • Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
  • Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

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.

aus demselben Repository

Weitere Skills

Alle Skills