Verified:GitHub

pr-review-expert

Reviews GitHub and GitLab pull requests with security scanning, blast radius analysis, and coverage checks.

2|Updated Mar 24, 2026

Search Tags:#diff analysis #code review #pull request #github #test coverage #security scan #gitlab

One-click install

npx skills add https://github.com/BryanPinheiro77/FinanceBot-BackEnd --skill pr-review-expert-bryanpinheiro77

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: pr-review-expert
Source: https://github.com/BryanPinheiro77/FinanceBot-BackEnd/tree/main/.agents/skills/pr-review-expert
Command: npx skills add https://github.com/BryanPinheiro77/FinanceBot-BackEnd --skill pr-review-expert-bryanpinheiro77

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing large or security-sensitive pull requests manually is slow and error-prone, and reviewers often miss breaking changes, security flaws, or missing tests hidden in big diffs. ## Core Features & Use Cases - Blast Radius Analysis: Traces which files, services, and shared contracts could break from a change, with severity ratings from CRITICAL to LOW. - Security & Breaking Change Detection: Scans diffs for SQL injection, hardcoded secrets, XSS vectors, removed API routes, and destructive DB migrations. - Test Coverage Delta: Compares new source code against new tests and flags uncovered logic or deleted tests. - Use Case: Before merging a 400-line PR that touches a shared auth library, run this review to get a prioritized report with MUST FIX, SHOULD FIX, and SUGGESTIONS sections plus a 30+ item checklist. ## Quick Start Review pull request 123 in this repository and produce a structured report covering security, breaking changes, and test coverage.

Frequently Asked Questions about pr-review-expert

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

FAQPage Schema

How do I review a GitHub pull request from the command line?▼

Use the gh CLI to fetch the diff and metadata: run gh pr diff <number> for the changes and gh pr view <number> --json title,body,labels for context. This skill then walks through blast radius, security, and coverage analysis on that diff.

How to detect security issues in a pull request diff?▼

Scan the diff with targeted grep patterns for SQL string interpolation, hardcoded secrets, AWS keys, XSS sinks like innerHTML, weak hashes such as md5, and eval or exec calls. Findings are classified by severity and reported as blocking or non-blocking.

Does this code review workflow support GitLab merge requests?▼

Yes, it supports GitLab through the glab CLI. Use glab mr diff <iid> to fetch the diff and glab mr view <iid> --output json for metadata, then the same analysis steps apply as for GitHub PRs.

How do I check if a PR introduces breaking API or database changes?▼

Look for removed routes, deleted TypeScript interfaces or GraphQL fields, and destructive migrations such as DROP TABLE or NOT NULL additions without defaults. The workflow also diffs referenced environment variables to catch config breakage.

When should a pull request be split instead of reviewed?▼

If a PR is too large to review properly in one pass, request that it be split into smaller changes. Reviewing oversized PRs superficially leads to missed blast radius impacts and untested error paths.