pr-reviewlisted

# /pr-review — Address PR Comments Fetch PR review comments via `gh`, address each one with code fixes, run tests, commit, and push. Systematic process to ensure no comment is missed. ## When to Use - After receiving review feedback on a pull request - When a PR has unresolved comments that need code changes - When iterating on a PR after reviewer suggestions ## Protocol ### 1. Fetch Comments ```bash # Get PR number from current branch PR_NUMBER=$(gh pr view --json number -q '.number') REPO=$(gh repo view --json nameWithOwner -q '.nameWithOwner') # Fetch all review comments (inline code comments) gh api repos/$REPO/pulls/${PR_NUMBER}/comments --paginate # Also fetch general PR comments (top-level discussion) gh api repos/$REPO/issues/${PR_NUMBER}/comments --paginate # Check for requested changes gh pr view $PR_NUMBER --json reviews -q '.reviews[] | select(.state == "CHANGES_REQUESTED") | .body' ``` ### 2. Inventory Comments List every comment with: - **File and line** — where the comment applies - **Author** — who made the comment - **Content** — what they said - **Status** — resolved/unresolved Group comments by file for efficient addressing. ### 3. Address Each Comment For each unresolved comment: 1. Read the relevant code context 2. Understand the reviewer's concern 3. Implement the fix or improvement 4. If you disagree with the suggestion, explain why in a reply rather than silently ignoring it ### 4. Test Run the project's test suite to confirm changes don't