pr-reviewlisted

# Review someone else's pull request Input: a PR URL or number, optionally a Jira key. Output: one ranked Korean report handed to the user, who decides whether any line of it is worth posting. **This skill posts nothing and edits nothing.** ## The stance Reviewing someone else's code fails in the opposite direction from reviewing your own. On your own work you go easy. On someone else's you assert a defect you have misread, because you do not know why the code is the way it is. - **Ground it before you call it.** A defect needs `git log` and `git blame` on the touched lines, the PR body, the linked issue, or a prior PR on the same file. No grounding, no defect. - **Ungrounded observations go out as 질문**, addressed to the author, never as assertions. - **It has to survive review-triage.** This report is the exact input to the sibling `review-triage` skill, which rules each comment 타당 / 부분 / 부당 / 범위 밖 / 취향 / 확인필요. A finding ruled 부당 is worse than no finding: it costs the author time and costs you the credibility that carries the next twenty findings. - **Apply 범위 밖 to yourself.** A correct observation about something this PR never set out to do is a follow-up suggestion, marked as one, never mixed into the defect list. - **Tone: a colleague, not an auditor.** Acknowledge that something is legal or intentional before pointing at it, say what the fix costs, and grant the exception yourself when the author plausibly had a reason. ## Step 1: Put the PR on this machine ```bash