Verified:GitHub

pr-review-expert

Analyze GitHub PRs and GitLab MRs for security, breaking changes, and test coverage.

2|Updated Mar 13, 2026

Search Tags:#automation #quality assurance #code review #github #pr review #security scanning #gitlab

One-click install

npx skills add https://github.com/zhangzhang-111-i/claude-skills111 --skill pr-review-expert

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: pr-review-expert
Source: https://github.com/zhangzhang-111-i/claude-skills111/tree/main/engineering/pr-review-expert
Command: npx skills add https://github.com/zhangzhang-111-i/claude-skills111 --skill pr-review-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of reviewing GitHub Pull Requests and GitLab Merge Requests, ensuring code quality, security, and adherence to best practices before merging.

Core Features & Use Cases

Comprehensive Analysis: Performs blast radius analysis, security scanning, breaking change detection, and test coverage checks.
Structured Reporting: Generates a reviewer-ready report with a detailed checklist and prioritized findings.
Use Case: Before merging a critical feature update, use this Skill to automatically scan the PR for potential security vulnerabilities, assess the impact on other services, and verify adequate test coverage.

Quick Start

Use the pr-review-expert skill to analyze pull request number 123.

Frequently Asked Questions about pr-review-expert

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

FAQPage Schema

How do I automate code review for GitHub PRs?▼

Automate GitHub PR code review by analyzing blast radius, security vulnerabilities, breaking changes, and test coverage deltas. The skill generates a structured report with a prioritized checklist for efficient merging decisions.

What does automated blast radius analysis do for a GitLab merge request?▼

Blast radius analysis for a GitLab MR evaluates the potential impact of code changes on other services before merging. It systematically identifies security vulnerabilities and breaking changes to ensure code quality and adherence to best practices.

Can I check test coverage deltas and security vulnerabilities before merging?▼

Yes, test coverage deltas and security scanning are checked automatically before merging. The analysis detects potential vulnerabilities and verifies adequate test coverage, outputting a reviewer-ready report with prioritized findings.

How do I get a structured code review report with a checklist?▼

Generate a structured code review report by running automated checks on your pull request or merge request. The output provides a detailed checklist and prioritized findings for security, breaking changes, and coverage.

Does this automated code review work for both GitHub and GitLab?▼

Yes, automated code review works for both GitHub Pull Requests and GitLab Merge Requests. It systematically analyzes blast radius, security vulnerabilities, and test coverage across both platforms.

What are the limitations of automated security scanning for pull requests?▼

Automated security scanning for pull requests focuses on blast radius, breaking changes, and coverage deltas but does not replace manual review entirely. It provides prioritized findings to guide reviewers, requiring human judgment for final merge decisions.