code-review-annotator

Read inline code review comments left by a human reviewer in the browser, then apply the requested fixes. Comments carry a scope (line / file / multi-file / view), one or more anchors (file + optional line range + blobSha + anchorText), and a viewContext saying which view the reviewer was in (tool-call / git-range / browse). Use when the user asks to "fix review comments", "apply review feedback", "read the review", or "address comments". Requires the code-review MCP server to be connected.

Print a one-screen situational summary of the current code review state — open vs resolved comment counts, the files most-commented-on, recent reviewer activity, orphan tool calls, and threads where Claude has replied but the human hasn't acknowledged. Use when the user asks "what's the review status", "any open comments", "where am I in the review", "summary of the queue", "anything pending", or just wants to pick the work back up after a break. Read-only — does not edit files, reply, or resolve.

Read every open code review comment, group them by risk / file / theme, and present a phased fix plan for the user to approve before any edits run. Use when the review backlog is large (rough cutoff ≥ 5 open comments), when the user says "triage the review", "plan the fixes", "what's the plan for the review backlog", "group these comments", or before invoking review-workflow on a big batch. Requires the code-review MCP server to be connected. Read-only — does not edit files or call mark_resolved.