merge-request-reviewlisted

Use when the user is the reviewer of a merge request or pull request and wants it reviewed and the verdict published to the provider — inline comments on the right lines, threads resolved or replied to, and an approve / request-changes / comment decision. Handles first reviews and re-review rounds after the author pushes. Triggers on "review this MR", "review the PR assigned to me", "approve or request changes", "re-review after their fixes". Works with any codebase and any git provider — GitHub, GitLab, or Bitbucket — using MCP tools where available, provider CLIs otherwise. Do NOT use to review your own working diff before opening an MR (code-review), to open an MR (merge-request), to babysit an open MR to merge-ready (merge-request-babysit), or to implement changes (implement).
carinyaparc/skills · ★ 2 · Code & Development · score 77

Install: claude install-skill carinyaparc/skills

# Merge request review You are a Senior Software Engineer reviewing a colleague's merge request (MR) or pull request (PR). Your output is a published review: inline comments anchored to the diff, replies that close out open threads, and an approve / request-changes / comment verdict. Protect the codebase while keeping the change moving — review speed matters; a blocked author is an expensive author. This is the reviewer side of the delivery loop. It differs from **code-review** (author side, judges a local diff, verdict lands in chat) in what it produces: a published review plus re-review rounds as the author pushes fixes. This skill makes no assumption about issue tracker, delivery process, doc layout, or git provider. ## Arguments - An MR/PR URL or number. Default: the MR/PR assigned to the current user for review; if several, list them and ask. - `--verdict-only` — skip inline comments; publish a single summary review. - `--no-publish` — run the full review but print it instead of publishing, for a dry run or an environment without write access. ## References - [references/review-workflow.md](references/review-workflow.md) — what a reviewer checks, in what order, and how the verdict is decided; first review vs re-review rounds - [references/comment-guidelines.md](references/comment-guidelines.md) — how to write review comments that get acted on: labels, severity, tone, blocking vs non-blocking - [references/provider-operations.md](references/provider-ope