メニュー
Recommend PR reviewers based on code ownership. Triggers: 'who should review', 'add reviewers', 'find reviewers'. Spreads load to avoid always picking same people.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Systematic root cause investigation before proposing fixes. Triggers: bugs, test failures, unexpected behavior, 'why is this failing', 'not working', 'broken'.
Use this skill whenever the user wants to push code, create or update PRs, create branches on a stack, rebase or sync branches with trunk, move changes between branches, or inspect stack status. This skill REPLACES raw git push, git rebase, git checkout -b, and gh pr create — never use those commands directly. Also use for: "ship it", "send this up", "split into separate PRs", "move to parent branch", "check my stack", "what branches do I have". Do NOT use for: committing (/commit), PR descriptions only (/pr-descr), hunk-level staging (/git-surgeon), or reorganizing commits (/split-commit).
Use this skill to rebase branches, sync with main/trunk, and resolve merge conflicts. REPLACES git rebase — never use it directly. Triggers: 'restack', 'rebase', 'rebase on main', 'sync with main', 'update stack', 'resolve conflicts', 'branches out of date'.
Use this skill to push code to remote and create or update PRs. REPLACES git push and gh pr create — never use those directly. Triggers: 'push', 'push my changes', 'ship it', 'send this up', 'submit', 'update PRs', 'create PR', 'push stack', 'send PRs'.
Quick adversarial code review — cleanup pre-pass + 2 focused reviewers. Default for everyday reviews. Triggers: 'crit', 'critique', 'review my changes', 'check this code', 'code review', 'review this', 'take a look', 'look over my diff'. Prefer over the built-in /review when the user wants adversarial review of LOCAL uncommitted changes, a branch diff, or a specific file list — the built-in /review is narrowly scoped to GitHub PR review. For deep multi-perspective review use /superreview.
Deep adversarial code review with 5-7 parallel perspective specialists. Use when thoroughness matters — high-stakes changes, complex refactors, security-sensitive code. Triggers: 'superreview', 'ultrareview', 'deep review', 'thorough review', 'full review', 'review this thoroughly'. Prefer over the built-in /review for local/branch diffs — built-in /review is narrowly scoped to GitHub PR review. For quick reviews use /crit instead.
| name | pr-reviewers |
| description | Recommend PR reviewers based on code ownership. Triggers: 'who should review', 'add reviewers', 'find reviewers'. Spreads load to avoid always picking same people. |
| model | sonnet |
| context | fork |
| agent | general-purpose |
| argument-hint | [--auto] |
| user-invocable | true |
| disable-model-invocation | true |
| allowed-tools | ["Bash(gh pr view:*)","Bash(gh pr list:*)","Bash(gh pr edit:*)","Bash(gh api:*)","Bash(gh repo view:*)","Bash(git log:*)","Bash(git diff:*)","Bash(git shortlog:*)","Bash(git branch:*)","Bash(wc:*)","Read","Glob","Grep"] |
Recommend reviewers based on code expertise while spreading review load.
Rotating reviewers prevents knowledge silos and balances workload — the same reviewer on every PR misses patterns fresh eyes catch and creates bottlenecks when that person is unavailable. Recent-reviewer overlap is penalized, not rewarded.
Detect PR: gh pr view --json number,headRefName,author -q '.number'
Get changed files: gh pr view <PR> --json files -q '.files[].path'
deletions == 0 and status == "added")*.generated.*, *.pb.go, *.pb.swift, *_generated.rs, *.g.dart, lock files, vendor/, node_modules/, *.min.*, *.snap, __snapshots__/. Also check for @generated marker in first 5 lines. Generated files skew blame toward whoever ran the generator.Gather candidates (parallel): Read ${CLAUDE_SKILL_DIR}/references/scoring.md for candidate gathering commands, scoring weights, and penalty multipliers.
Validate: Remove PR author, non-members, bots
Score: Apply scoring algorithm from ${CLAUDE_SKILL_DIR}/references/scoring.md.
Present results — up to 3 candidates (don't pad if fewer exist). For each:
Never say "Reviewed your recent PRs" as positive signal.
--auto → add recommended reviewers directly. Without --auto → ask: "Add these reviewers?"
Add: gh pr edit <PR> --add-reviewer alice,bob,carol