skills.rest
DoctorMozg
DoctorMozgCOMMUNITY
Explore all skills by this author →
GitHub

github-review-pr

Reviews a GitHub pull request via a dispatched agent and writes a severity-labeled report.

2|Updated Apr 4, 2026
Search Tags:#code review#pull request#github#pr review#gh cli#agent dispatch#severity findings
One-click install
npx skills add https://github.com/DoctorMozg/claude-pipelines --skill github-review-pr-doctormozg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-review-pr
Source: https://github.com/DoctorMozg/claude-pipelines/tree/main/plugins/mz-dev-git/skills/github-review-pr
Command: npx skills add https://github.com/DoctorMozg/claude-pipelines --skill github-review-pr-doctormozg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reviewing GitHub pull requests thoroughly requires checking diffs, CI results, and multiple code lenses, which is slow and error-prone when done manually. This Skill automates the entire review by dispatching a specialized agent that produces a structured report with severity-labeled findings and a verdict. ## Core Features & Use Cases - Agent-Dispatched PR Review: Launches the github-pr-reviewer agent in an isolated worktree to analyze the PR with multi-lens fan-out and CI cross-referencing. - Structured Reports: Writes findings to .mz/reviews/ with Critical/severity labels and a VERDICT line for quick decision-making. - Robust Escalation: Validates PR accessibility via gh, MCP GitHub tools, or the REST API, and escalates ambiguous or blocked cases instead of guessing. - Use Case: Given a PR URL like https://github.com/owner/repo/pull/123, run the review and receive a report path plus the count of Critical findings before merging. ## Quick Start Ask the assistant to review the pull request at https://github.com/owner/repo/pull/123 and show the verdict and critical findings.

Frequently Asked Questions about github-review-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a GitHub pull request with an AI agent?▼

Provide a PR URL or owner/repo#number reference and the skill dispatches the github-pr-reviewer agent in an isolated worktree. It returns a report under .mz/reviews/ with severity-labeled findings and a verdict line.

What PR reference formats are accepted for review?▼

Two formats are accepted: a full URL like https://github.com/owner/repo/pull/123, or the short form owner/repo#123. If the argument is missing or malformed, the skill asks for clarification rather than guessing.

What happens if the gh CLI is not available during PR review?▼

The skill falls back to MCP GitHub tools if exposed, then to the GitHub REST API via curl with a GITHUB_TOKEN. It only escalates to the user after all three access tiers fail.

When should I use review-branch instead of reviewing a GitHub PR?▼

Use review-branch when the changes live on a local branch rather than a GitHub pull request. For triaging many PRs at once, use github-scan-prs instead of reviewing them individually.

What does the PR review report contain?▼

The report is written to .mz/reviews/ with a dated filename and contains severity-labeled findings plus a VERDICT line. The skill prints the report path, the verdict, and the count of Critical findings.

Related Skills

Explore More Software Engineering Skills→
bravrosbravros
3

address-pr

Fetch GitHub PR review comments, implement the fixes, push, and route the next workflow step.

Official
Advanced
cogpycogpy

prepare-pr

Rebase GitHub pull requests onto main, apply review fixes, and run automated gates.

Official
Advanced
XiaoPuOuOXiaoPuOuO
1

verification-loop

Runs build, type-check, lint, tests, security scans, and diff reviews across JavaScript/TypeScript and Python projects.

Community
Advanced
mozillamozilla
685

fxa-pr-status

Lists open Mozilla FXA pull requests with review status in a markdown table.

Official
Intermediate