address-reviewlisted

# Address review Work through the open review comments on your own pull request: triage every comment into a table, fix everything that needs no human input, then bring the blockers and the decisions to the human one at a time. ## When to use - "What did the reviewers say and can you fix it?" - "Address the comments on PR 412." - "Reply to these threads and mark them resolved." - "Address the review comments" with no PR named, while sitting in the branch's checkout or worktree. Do not use this when the user wants to **review** someone else's PR and leave feedback. That is the `review-pr` skill. ## Prerequisites ```bash gh auth status # must be logged in ``` If `gh` is missing or unauthenticated, stop and tell the user; do not guess at PR content. **Command economy is a hard requirement.** Every script here batches into a single API call. Never loop a command per thread, and never dump raw JSON into context. ## Workflow The triage table is built first and drives everything after it. Do not start editing code before the table is complete. ### 0. Identify the PR When the user gives a PR URL or number, use it and skip to step 1. When they do not, resolve the PR from the branch checked out in the current directory, which works the same in a plain clone and in a `git worktree`. `gh` reads the branch of the working directory it runs in: ```bash gh pr view --json number,title,headRefName,url,state --jq '"\(.number)\t\(.state)\t\(.headRefName)\t\(.title)"' ``` Conf