本文へ移動
cccskills
無料GitHub で公開

gitnexus-pr-swarm-review

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

インストール方法を見る

含まれるファイル(1)

  • SKILL.md1.6 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

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"

日本語の概要は準備中です。原文の説明を表示しています。

abhigyanpatwari/GitNexus4.8万2026年10月13日 更新

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"

日本語の概要は準備中です。原文の説明を表示しています。

abhigyanpatwari/GitNexus4.8万2026年10月13日 更新

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"

日本語の概要は準備中です。原文の説明を表示しています。

abhigyanpatwari/GitNexus4.8万2026年10月13日 更新

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?"

日本語の概要は準備中です。原文の説明を表示しています。

abhigyanpatwari/GitNexus4.8万2026年10月13日 更新

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?"

日本語の概要は準備中です。原文の説明を表示しています。

abhigyanpatwari/GitNexus4.8万2026年10月13日 更新

Use when the user wants the GitNexus engineering pipeline run end-to-end on a task: gitnexus-plan (plan depth chosen up front), a blocking gate to execute with gitnexus-work or stop, finishing with a gitnexus-review of the result. Examples: "/gitnexus-lfg Add retry support to the ingestion pipeline", "run the gitnexus pipeline on this", "plan, build and review this feature".

日本語の概要は準備中です。原文の説明を表示しています。

abhigyanpatwari/GitNexus4.8万2026年10月13日 更新

abhigyanpatwari のスキルをすべて見る

このスキルの問題を報告する