pr-review-expert

Analyze GitHub and GitLab pull request diffs for security and breaking changes.

Updated Nov 3, 2016

Search Tags:#quality assurance #code review #pull request #github #security scan #gitlab #blast radius

One-click install

npx skills add https://github.com/xleliberty/mydotfiles --skill pr-review-expert-xleliberty

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: pr-review-expert
Source: https://github.com/xleliberty/mydotfiles/tree/main/.config/.claude/plugins/cache/claude-code-skills/engineering-advanced-skills/2.1.2/pr-review-expert
Command: npx skills add https://github.com/xleliberty/mydotfiles --skill pr-review-expert-xleliberty

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, glab, jq.

What problem does it solve?

This skill addresses the inconsistency and superficiality of manual code reviews by providing a structured, data-driven framework that identifies security vulnerabilities, breaking changes, and performance regressions before they reach production.

Core Features & Use Cases

Blast Radius Analysis: Automatically maps the impact of changes across services, shared libraries, and database schemas.
Security & Quality Scanning: Detects common vulnerabilities like SQL injection, secret exposure, and N+1 query patterns.
Use Case: Use this skill when reviewing large pull requests in a monorepo to ensure that a change in a shared utility library does not inadvertently break downstream services or introduce security flaws.

Quick Start

Use the pr-review-expert skill to perform a comprehensive review of the pull request with ID 123 by fetching its diff and analyzing it against the security and blast radius checklists.

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 pull requests to find security vulnerabilities?▼

Automated code review analyzes pull request diffs to detect security vulnerabilities like SQL injection and secret exposure. It fetches PR metadata using gh or glab CLI tools, then systematically assesses the diff against security and blast radius checklists.

What is blast radius analysis in a monorepo and how does it prevent breaking changes?▼

Blast radius analysis maps the impact of changes across services, shared libraries, and database schemas. It prevents breaking changes by identifying how a modification in a shared utility library affects downstream services before reaching production.

Do I need gh or glab CLI installed to review GitHub and GitLab pull requests?▼

Yes, you need gh or glab CLI installed to review GitHub and GitLab pull requests. The skill requires these CLI tools and jq to fetch PR metadata and diffs for automated assessment of security vulnerabilities and performance regressions.

Can I detect test coverage gaps and performance regressions in a code diff?▼

Yes, you can detect test coverage gaps and performance regressions in a code diff. The review process analyzes the fetched diff for N+1 query patterns and other quality issues alongside security flaws and breaking changes.

What's the best way to review large pull requests for quality assurance?▼

The best way to review large pull requests for quality assurance is using a structured, data-driven framework that evaluates diffs against security and blast radius checklists, replacing inconsistent manual code reviews with systematic assessment.