pr-review-expert

Analyze pull requests for correctness, security risks, breaking changes, and test coverage.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken releases and security regressions by turning PR review into a structured, evidence-based assessment of impact, risk, and verification coverage.

Core Features & Use Cases

  • Blast radius analysis: identifies direct dependents, service boundary crossings, and shared contract changes to estimate rollout risk.
  • Security scanning: checks for common vulnerability patterns such as SQL injection, hardcoded secrets, XSS vectors, auth bypass, dangerous eval/exec, weak hashes, path traversal, and prototype pollution.
  • Test coverage delta: compares changed source vs test files and flags missing or removed coverage, especially for auth/payments paths.
  • Breaking change detection: reviews endpoint/request/response contract changes, exported TypeScript types, and DB migration rollback safety.
  • Performance impact checks: looks for N+1 query patterns, unbounded loops, missing awaits, and dependency bloat.
  • Use case: a team reviewing a large PR touching shared auth logic and database schema can quickly produce a reviewer-ready report with MUST/FIX and SHOULD/FIX items before merge.

Quick Start

Use the pr-review-expert skill to generate a complete PR review report for your current diff and produce a prioritized list of blocking and non-blocking issues.

Frequently Asked Questions about pr-review-expert

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

FAQPage Schema
How do I analyze a pull request for breaking changes and security risks before merging?

To analyze a pull request for breaking changes and security risks, you gather diff-based context to classify blast radius, scan for vulnerability patterns like SQL injection, and compute test coverage deltas to produce a reviewer-ready checklist.

What is blast radius analysis in code reviews and when do I need it?

Blast radius analysis in code reviews identifies direct dependents, service boundary crossings, and shared contract changes to estimate rollout risk. You need it when reviewing large PRs or security-sensitive modifications before merge.

How can I detect breaking changes in API contracts and database migrations during a PR review?

Detecting breaking changes in API contracts and database migrations requires reviewing endpoint request and response contract modifications, exported TypeScript types, and verifying DB migration rollback safety within the PR diff.

How to check test coverage impact for auth and payment paths in a pull request?

Checking test coverage impact involves comparing changed source files against test files to flag missing or removed coverage, prioritizing critical paths like authentication and payment logic to ensure verification completeness.

Does this PR review process check for performance issues like N+1 queries and missing awaits?

Yes, the PR review process includes performance impact checks that look for N+1 query patterns, unbounded loops, missing awaits, and dependency bloat to ensure code modifications do not introduce latency bottlenecks.

What is the best way to review large PRs touching shared auth logic and database schema?

The best way to review large PRs touching shared auth logic and database schema is to generate a structured report with blast radius classification, security scanning, and a prioritized list of MUST/FIX and SHOULD/FIX items before merge.