review-triagelisted

Triage the review comments on your pull request. Fetches a PR's reviews (inline code comments, review summaries, and PR-level comments, from humans and bots) and, for each, gives an easy Korean summary, then judges it on the evidence (the actual code, the manual/spec, and this PR's own scope) instead of on the reviewer's authority, and either drafts a fix plan (valid) or a reasoned reply saying why not (wrong, already handled, out of scope, or style). Analysis and drafts only: it does not post replies or change code. Use when your PR has review feedback you want to understand and respond to. Triggers on phrases like 'PR 리뷰 정리해줘', '리뷰 코멘트 타당한지 봐줘', '리뷰 대응', 'triage my PR reviews', 'help me respond to PR review'.
Srltas/claude-skills · ★ 0 · Code & Development · score 67

Install: claude install-skill Srltas/claude-skills

# 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`. **No separate lookup is needed**: Step 2 prints the title, base, and body along with the reviews. Those state **what this PR set out to do**, which Step 3 judges scope against. If the body links an issue (CBRD, APIS, TOOLS, HHH), pull it too (**jira-fetch** for CUBRID Jira Server keys, publicly readable projects only) so the PR's intent comes from the issue, not from a guess. ## Step 2: Fetch the reviews ```bash bash <skill-base-dir>/assets/fetch_reviews.sh [PR] [--include-resolved] ``` 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`. **Comments in resolved review threads are skipped**: that discussion is already settled, so re-judging it wastes effort and reopens closed points. The script prints how many it skipped; pass `--include-resolved` when you do want to revisit them (say, to check that a resolved thread was actually addressed). Threads that are merely **outdated** (the diff moved) are still shown: outdated is not resolved. If `$ARGUMENTS` is a full PR URL, its owner