address-copilot-reviewlisted

# Address Copilot review Take a PR through Copilot's code review end to end: check it out, read every Copilot comment, investigate the code to judge each one, apply the fixes you agree on, commit and push, then reply to and resolve each thread. Mechanics worth knowing up front: GitHub's REST API posts replies, but **thread resolution is GraphQL only**. ## Golden rules - **Pause before any GitHub write.** Investigate and present a per-comment assessment first; only apply fixes / commit / push / reply / resolve after the user approves. - **Ask on every disagreement.** If a comment looks wrong, not applicable, or a false positive, surface it and let the user decide. Never silently dismiss or resolve it. - Match each fix to the comment it addresses. One commit referencing the review is usually enough. - Only resolve threads you actually addressed (or that the user told you to close). Leave disputed threads open unless the user says otherwise. ## Workflow ### 1. Check out the PR Accepts a PR number, URL, or defaults to the current branch's PR. ```bash gh pr checkout <PR> gh pr view <PR> --json number,title,headRefName,url ``` ### 2. Read the Copilot review Summary review (the overview + finding count): ```bash gh pr view <PR> --json reviews \ --jq '.reviews[] | select(.author.login=="copilot-pull-request-reviewer") | .body' ``` Inline findings (the actionable comments; top-level only, skip replies): ```bash gh api repos/{owner}/{repo}/pulls/<PR>/comments --paginate \ --