handover-reviewlisted

# Review Handover context Keep feedback attached to the exact artifact and revision that was reviewed. Requires a configured Handover MCP connection. Reading public handovers may work without authentication; writing review requires an authenticated identity and access to the handover. If Handover MCP is not configured, direct the user to `https://handover.sh/install?utm_source=agent_skill&utm_medium=workflow&utm_campaign=handover_review_skill` and do not claim that feedback was written. Use the smallest workspace access that permits the requested review. Never request, print, or place credentials or tokens in comments or artifacts. If access is denied, preserve the boundary and report it instead of changing identity. ## Establish review context 1. Call `handover.whoami` before authenticated review work. 2. Resolve the handover with `handover.search` or `handover.get`. 3. Record the current revision identifier. 4. Read the target artifact with `handover.read_artifact`. 5. Retrieve its thread and existing annotations with `handover.thread` and `handover.annotations`. Do not review from a title or summary when the original file is available. ## Choose comment or annotation Use `handover.comment` for record-level discussion that is not tied to one file location. Use `handover.annotate` when feedback concerns: - selected text; - a code or document line range; - an image region; - an entire artifact at a specific revision. An actionable review item states the problem