| 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. |
PR Reviewer
Routing
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 | |
Auto-Detection
Before dispatching to any sub-command, confirm a PR is attached to the current branch:
gh pr view --json number,state 2>/dev/null
- PR exists โ proceed with routing
- No PR โ stop: "No open PR found for the current branch."
Workflow Sequence
The three sub-commands map to the natural reviewer lifecycle:
digest โ write โ followup
(์ดํด) (๋ฆฌ๋ทฐ) (๋ฐ์ ํ์ธ)
Each phase is independent โ the operator can enter at any point.
Language
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.