abhigyanpatwari/gitnexus

gitnexus-pr-swarm-review

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

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/abhigyanpatwari/gitnexus --skill gitnexus-pr-swarm-review

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

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.

同じリポジトリから

関連する Skills

すべての Skills
abhigyanpatwari
コミュニティ

gitnexus-cli

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

1時間の導入数
1
GitHub Stars
4.9万
更新日
11月17日
abhigyanpatwari
コミュニティ

gitnexus-debugging

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

1時間の導入数
1
GitHub Stars
4.9万
更新日
11月17日
abhigyanpatwari
コミュニティ

gitnexus-refactoring

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

1時間の導入数
1
GitHub Stars
4.9万
更新日
11月17日
abhigyanpatwari
コミュニティ

gitnexus-exploring

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

1時間の導入数
1
GitHub Stars
4.8万
更新日
11月4日