code-reviewlisted

# PR Code Review Skill Use this skill when asked to review one or more pull requests. It covers reading diffs, forming opinions, and posting structured feedback. --- ## Step 0 — Verify `gh` auth Run `gh auth status`. If unauthenticated, tell the user and stop — do not attempt to read diffs or post comments without it. ## Step 1 — Identify the PR(s) - If the user provides one or more PR numbers or URLs, use those directly. - If no PR is specified, ask the user: "Which PR(s) should I review? (number, URL, or branch name)" - If a PR is in **draft** state, note it. Default the verdict to `COMMENT` — do not APPROVE or REQUEST_CHANGES a draft. - If multiple PRs are provided, determine the relationship before proceeding: - **Stacked PRs** (each targets the previous branch): review them in order, treating each diff as a layer on top of the previous. Note cross-PR issues explicitly. - **Parallel PRs** (same feature, split by concern): review each independently, then write a combined summary that calls out any integration concerns. - **Unrelated PRs**: review each fully and independently. Produce a separate summary per PR. State your interpretation to the user before proceeding. ## Step 2 — Gather context For each PR: 1. Fetch the PR metadata: title, description, linked Jira ticket (if any), target branch. 2. Read the full diff using `gh pr diff <number>`. 3. For any function renamed, contract changed, or public API modified: use `grep`/`Glob` to find callers and read