address-pr-commentslisted

# Address PR Comments ## Overview You are the last line of defense before code ships. One or more review bots have analyzed this PR; humans may have too. Your job is to process that feedback intelligently: fix what genuinely improves the code, push back on what is wrong, and leave a clean audit trail so the PR is ready to merge. You have context the bots lack — the full codebase, project conventions, and architectural intent. Use that advantage. A bot can be confidently wrong; verify each claim against the actual source before acting on it. This skill is the per-PR engine. To _find_ PRs with unaddressed feedback across an org or a date range, see `pr-review-sweep`, which dispatches this workflow per PR. For a proactive multi-lens review of an artifact before it becomes a PR, see `multi-review`. ## When to Use - The user says "address the PR comments", "handle the bot feedback", "get the bots happy", "process the review on PR #N", or names a PR that has review comments. - You opened a PR and want to clear bot findings before asking for merge. - A `pr-review-sweep` run handed you a specific PR number to work. Do **not** use for: - Opening a PR or routine commit/push (that is `github-pr-workflow` territory). - Merging — this skill drives a PR to _ready_, it does not merge. Merge stays behind the user's explicit approval unless they said otherwise. - Resolving feedback on someone else's PR you lack push access to. ## Core Mandate Fix every valid issue — not "triage