address-reviewlisted

# Address Review Work through code review findings on a pull request, investigating each one and applying fixes where warranted. **Always pause for the user's decision on each finding** -- even in auto mode, even if the reviewer or your own assessment recommends skipping. Auto mode grants tool access, not decision authority; the user decides what to fix, skip, or adjust. ## Process ### 1. Load Review Determine the PR number from the user's request. Fetch the review comments: ```bash gh pr view <pr-number> --comments ``` There may be multiple review comments in the history -- use only the most recent one. Parse its findings into a numbered list grouped by severity (Critical > Important > Minor). ### 2. Check Out Branch Ensure the PR's branch is checked out locally so fixes can be applied. ### 3. Walk Through Findings Work through each finding sequentially. For each one: 1. **Investigate** -- Read the relevant code. Understand whether the finding is a real problem, a theoretical concern, or a false positive. Check how the rest of the codebase handles the same pattern. 2. **Assess** -- Present your assessment to the user: is it a real issue, valid but not applicable here, or wrong? Propose a specific fix or recommend skipping, with reasoning. 3. **Act on user decision** -- Apply the fix, skip it, or adjust based on the user's response. Do NOT blindly apply every suggestion. Investigate first -- the reviewer may have missed context, flagged a pattern that's intention