メニュー
Use when reviewing someone else's PR at any stage of the review lifecycle — digest a PR, write a review, or verify follow-up changes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user explicitly runs /setup-precommit to install or refresh a quiet, staged-only git pre-commit hook (secretlint → oxlint → oxfmt) wired through package.json "prepare". User-invoked command only, never auto-triggered.
Use when the user asks to create, make, or start a new branch (e.g. `/branch`), or wants a conventional-commit-style branch name generated from the current work.
Use when auditing or improving an agent skill package before it ships or is handed off.
Use when the user is working on their own PR — drafting/creating it, handling reviewer comments, verifying fixes, or requesting re-review.
Use when fixing a bug, refactoring existing code without changing its behavior, or adding a feature that extends existing behavior — any code change that needs a verifiable foundation before the change is made.
Use when the user wants to A/B test prompts or workflows, validate behavioral equivalence, or stress-test non-deterministic outputs at scale via repeated multi-agent runs.
| name | pr-reviewer |
| description | Use when reviewing someone else's PR at any stage of the review lifecycle — digest a PR, write a review, or verify follow-up changes. |
Determine the sub-command from args or conversation context:
| Trigger | Sub-command | Action |
|---|---|---|
digest, "PR 파악", "PR 이해", "멘탈모델", wants to understand before reviewing | digest | Read and follow digest/index.md |
write, "리뷰 작성", "코드 리뷰", "review", wants to leave review comments | write | Read and follow write/index.md |
followup, "반영 확인", "follow-up", "re-review", checking author's fixes | followup | Read and follow followup/index.md |
| (no arg, ambiguous) | Ask the operator which phase they're in |
Before dispatching to any sub-command, confirm a PR is attached to the current branch:
gh pr view --json number,state 2>/dev/nullThe three sub-commands map to the natural reviewer lifecycle:
digest → write → followup
(이해) (리뷰) (반영 확인)
Each phase is independent — the operator can enter at any point.
Detect the operator's conversation language. All generated content (summaries, comments, reports) MUST use that language. Preserve source-code artifacts (file paths, identifiers, diff hunks) in their original language.