pr-review-expert

Review pull requests and merge requests for code quality, security, and breaking-change risks.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/mdnaimul22/human-skills --skill pr-review-expert-mdnaimul22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review-expert
Source: https://github.com/mdnaimul22/human-skills/tree/main/skills/pr-review-expert
Command: npx skills add https://github.com/mdnaimul22/human-skills --skill pr-review-expert-mdnaimul22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you review pull requests and merge requests in a structured way so you can catch correctness, security, breaking-change, and quality issues before they reach production.

Core Features & Use Cases

  • Blast radius analysis: traces changed files to likely dependents, service boundaries, and shared contracts to estimate impact.
  • Security scanning: identifies common high-risk patterns (injection, auth bypasses, secret exposure, unsafe hashing, XSS vectors, and dangerous exec usage).
  • Test coverage delta & quality assurance: compares changed logic vs changed tests and flags missing coverage for new/changed behaviors.
  • Breaking change detection: checks API contract, DB migration/destructive changes, and environment/config compatibility risks.
  • Performance impact checks & review-ready reporting: evaluates regressions like N+1 patterns, heavy dependency additions, unbounded loops, and missing awaits.

Quick Start

Ask your AI to run the PR Review Expert on PR #123 by fetching the diff and producing a prioritized reviewer-ready report with blast radius, security findings, test/coverage delta, breaking changes, and performance risks.

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 pull request for breaking changes and security risks?

To review a pull request for breaking changes and security risks, you analyze the proposed diff to identify API contract violations, destructive database migrations, and high-risk security patterns like injection or auth bypasses.

What is blast radius analysis in merge request reviews?

Blast radius analysis in merge request reviews traces changed files to likely dependents, service boundaries, and shared contracts to estimate the potential impact and severity of proposed code modifications.

How do I check test coverage delta for new code in a pull request?

To check test coverage delta in a pull request, compare the changed logic against the changed tests to flag missing coverage for newly introduced or modified application behaviors.

Does this structured impact assessment work with both GitHub and GitLab workflows?

Yes, structured impact assessment works with both GitHub and GitLab workflows by utilizing pull request and merge request metadata alongside diff content to produce reviewer-ready prioritized findings.

How do I detect performance regressions like N+1 queries when reviewing a diff?

To detect performance regressions like N+1 queries when reviewing a diff, evaluate the code changes for heavy dependency additions, unbounded loops, and missing awaits to prevent production slowdowns.

What is the best way to automate security pattern checks in a pull request review?

The best way to automate security pattern checks in a pull request review is to scan the diff content for unsafe hashing, secret exposure, XSS vectors, and dangerous exec usage to generate a prioritized report.