skills.rest
milistu
milistuCOMMUNITY
Explore all skills by this author →
Website𝕏@milistuuGitHub

pr-review

Generates structured analysis of pull requests highlighting risks and cross-file implications for reviewers.

7|Updated Feb 2, 2026
Search Tags:#analysis#explanation#pr#code-review#risk#pull-request
One-click install
npx skills add https://github.com/milistu/agent-skills --skill pr-review-milistu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/milistu/agent-skills/tree/main/skills/pr-review
Command: npx skills add https://github.com/milistu/agent-skills --skill pr-review-milistu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps reviewers quickly understand a pull request by providing a structured explanation of changes, the rationale, and potential risks.

Core Features & Use Cases

  • Clear change summaries: outlines what changed and why.
  • Risk and impact assessment: highlights potential issues and recommended actions.
  • Cross-file reasoning: shows how changes fit together and what to verify in tests.

Quick Start

Provide the PR number or branch name to generate a structured PR analysis and risk assessment.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I summarize pull request changes for code review?▼

To summarize pull request changes for code review, provide the PR number or branch name to generate a structured analysis. This outlines what changed, the rationale, and cross-file implications to speed up reviews.

What is the best way to assess risks in a pull request?▼

Assessing risks in a pull request involves highlighting potential issues and cross-file implications with clear references to exact code locations. This structured risk assessment guides reviewers on what to verify in tests.

How do I explain cross-file implications in a pull request?▼

Explaining cross-file implications in a pull request requires outlining how changes fit together and verifying testing status. This shows reviewers the broader impact of changes across the codebase.

Can I review large pull requests without duplicating PR descriptions?▼

Yes, you can review large pull requests without duplicating PR descriptions by generating a structured analysis of the rationale and risks. This guides reviewers through changes independently of existing PR text.

When do I need a structured explanation for a pull request?▼

You need a structured explanation for a pull request when reviewers must quickly understand changes, intent, and potential risks. This is applicable to code review tasks for PRs of varying size.

Related Skills

Explore More Software Engineering Skills→
0xdeafcafe0xdeafcafe

review-pr

Audit open GitHub pull requests and return structured read-only reviews.

Community
Advanced
sergicalsergical

sentry-pr-code-review

Parse Sentry bot comments in GitHub PRs to extract issues and suggested fixes.

Community
Advanced
aaddrickaaddrick
5.3k

lint

Lint shell scripts with shellcheck and GitHub Actions workflows with actionlint.

Community
Basic
michaelalbermichaelalber
2

dotnet-security-review

Review .NET applications for OWASP Top 10 vulnerabilities and Telerik CVEs.

Community
Advanced