pr-review-expert

Automates PR/MR reviews detecting risks, stability concerns and generating prioritized reports.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Scheune10-coding/my-claude-code-skills --skill pr-review-expert-scheune10-coding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review-expert
Source: https://github.com/Scheune10-coding/my-claude-code-skills/tree/main/pr-review-expert
Command: npx skills add https://github.com/Scheune10-coding/my-claude-code-skills --skill pr-review-expert-scheune10-coding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review can be time-consuming and error-prone; this Skill provides a structured, automated approach to PRs/MRs to surface risk early and ensure consistency.

Core Features & Use Cases

  • Blast radius analysis to identify impacted files, services, and downstream consumers.
  • Security scans for common weaknesses and vulnerability signals in PRs/MRs.
  • Test coverage delta calculation to gauge changes relative to tests.
  • Breaking change detection for API contracts, DB migrations, and config keys.
  • Ticket linking to verify related Jira/Linear tickets and alignment with scope.
  • Performance impact indicators such as potential N+1 queries or payload growth.

Quick Start

Analyze the PR/MR and return a reviewer-ready, prioritized report.

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 pull request reviews to identify blast radius and security risks?

Automating pull request reviews identifies blast radius, security risks, and stability concerns across codebases to surface risk early. It applies to monorepos, shared libraries, APIs, and database migrations, delivering a prioritized checklist with actionable recommendations.

How does breaking change detection work for API contracts and database migrations?

Breaking change detection for API contracts and database migrations scans pull requests to identify potential stability concerns. It evaluates modifications to configuration keys and database schemas to ensure downstream consumers remain unaffected by breaking changes.

Can I calculate test coverage delta to gauge changes relative to modified code?

Calculating test coverage delta measures test changes relative to modified code in pull requests. This capability evaluates whether submitted code modifications include sufficient test coverage to maintain stability across the codebase.

What is the best way to link Jira or Linear tickets to verify pull request scope alignment?

Linking Jira or Linear tickets verifies related tickets and ensures alignment with the intended scope of pull requests. This ticket linking capability checks that code changes directly correspond to defined project requirements and tracked issues.

Does this pull request review approach work for monorepos and shared libraries?

Pull request review works effectively for monorepos and shared libraries by analyzing impacted files, services, and downstream consumers. This blast radius analysis scales across codebases of varying size and complexity to identify stability concerns.

How do I detect performance impact indicators like N+1 queries in code reviews?

Detecting performance impact indicators like N+1 queries and payload growth happens during code reviews by analyzing pull requests. This automated process surfaces potential performance degradation early to ensure codebase stability.