review-triagelisted

# Triage PR review comments Pull the review feedback on your PR and, comment by comment, summarize it plainly, judge whether it holds up against the real code, and draft either a fix plan or a reasoned reply. Analysis and drafts only: it does not post anything or change code. ## Step 1: Identify the PR The current branch's PR by default, or a number/URL from `$ARGUMENTS`. ```bash gh pr view --json number,url,headRefName,baseRefName # current branch's PR ``` ## Step 2: Fetch the reviews ```bash bash <skill-base-dir>/assets/fetch_reviews.sh [PR] ``` Merges inline code comments, review summaries, and PR-level comments (humans and bots, shown as `(User)` / `(Bot)`) with thread/reply info. Needs `gh` (authenticated) and `jq`. ## Step 3: Judge each comment against the real code (grounding) For every comment, open the referenced `file:line` and the PR diff and check whether the point is actually correct. Do not agree or dismiss from memory: read the code. Separate real issues from style opinions, misunderstandings, or already-handled cases. Use cubrid-manual / cmt-manual to confirm a fact when the comment hinges on one. ## Step 4: Summarize and draft, per comment For each comment, output (요약/판정/계획 or 답변 in Korean for the user): - **요약**: what the reviewer is asking, in plain Korean. - **판정**: 타당(O) / 부당(X) / 부분(△), with a one-line 근거 grounded in the code. - if 타당 → **수정 계획**: which file and approach, briefly. - if 부당/부분 → **답변 초안**: a reasoned reply to post. Write the