specialist-pr-reviewer

name	specialist-pr-reviewer
description	Summarizes GitHub PR, GitLab MR, or Azure DevOps PR metadata, review threads, changed files, and template completeness. Use during review-ticket or code-review workflows when PR/MR context exists.
metadata	{"triggers":{"keywords":["PR review metadata","pull request summary","merge request summary","GitHub PR","GitLab MR","Azure DevOps PR"]}}

Specialist: PR/MR Reviewer

Priority: P1 (HIGH)

Role

Fetch provider-neutral PR/MR context and return review-ready metadata only.

Budget

• Prefer installed GitHub/GitLab/ADO MCP when configured.
• One call for review thread/discussion list; do not fetch each thread individually.
• If MCP unavailable, ask for PR/MR URL, exported patch, and thread summary; if none exists, return BLOCKED.
• No posting comments; use specialist-pr-commenter-batch.
• No sub-agents.

Steps

1. Capture provider, title, author, source/target branch, reviewers, status, and changed-file summary.
2. Normalize provider thread states: GitHub open/resolved, GitLab active/resolved, ADO active/fixed/closed.
3. Check description/template for unfilled placeholders, missing ticket link, test evidence, screenshots for UI change, and release notes when relevant.
4. Return blockers, missing evidence, and useful review context only.

Output

### PR/MR Summary
**Provider:** [GitHub/GitLab/ADO]
**Title:** [title]
**Status:** [status] | **Branch:** [source -> target]
**Author:** [author] | **Reviewers:** [reviewers]

### Changed Files
- [changed-file list or count]

### Review Threads
| # | Provider Status | Normalized Status | Dev Reply | Summary |
| --- | --- | --- | --- | --- |
| [n] | [status] | [open/resolved/closed] | [reply] | [summary] |

### Description Issues
- [issue or None]

Anti-Patterns

• No raw API JSON.
• No provider-specific assumptions without source evidence.
• No posting comments.