Agent Skills › abhigyanpatwari/GitNexus › gitnexus-pr-swarm-review

gitnexus-pr-swarm-review

GitHub

协调多智能体对 GitNexus PR 进行生产就绪评审。作为 Swarm 协调者，按顺序分发子代理执行审查，严格遵循只读原则，综合输出评审结果，确保代码质量与安全性。

.claude/skills/gitnexus-pr-swarm-review/SKILL.md abhigyanpatwari/GitNexus

Trigger Scenarios

需要全面评估 PR 生产就绪状态请求结构化、多视角的自动化代码审查

Install

npx skills add abhigyanpatwari/GitNexus --skill gitnexus-pr-swarm-review -g -y

More Options

Non-standard path

npx skills add https://github.com/abhigyanpatwari/GitNexus/tree/main/.claude/skills/gitnexus-pr-swarm-review -g -y

Use without installing

npx skills use abhigyanpatwari/GitNexus@gitnexus-pr-swarm-review

指定 Agent (Claude Code)

npx skills add abhigyanpatwari/GitNexus --skill gitnexus-pr-swarm-review -a claude-code -g -y

安装 repo 全部 skill

npx skills add abhigyanpatwari/GitNexus --all -g -y

预览 repo 内 skill

npx skills add abhigyanpatwari/GitNexus --list

SKILL.md

Frontmatter

{
    "name": "gitnexus-pr-swarm-review",
    "description": "Run a GitNexus production-readiness pull request review using a coordinated reviewer swarm."
}

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.