skills.rest
umputun
umputunCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pr

Analyze pull request diffs and discussions to surface code quality issues.

439|45|Updated Feb 17, 2026
Search Tags:#testing#architecture#review#diff#pr#code-review#ci
One-click install
npx skills add https://github.com/umputun/cc-thingz --skill pr-umputun
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/umputun/cc-thingz/tree/main/plugins/review/skills/pr
Command: npx skills add https://github.com/umputun/cc-thingz --skill pr-umputun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze PRs systematically to surface architecture, quality, and testing issues, enabling faster, higher-quality merges.

Core Features & Use Cases

  • Analyze PR metadata, diffs, and discussion to surface architecture and quality concerns
  • Detect scope creep, unresolved questions, and potential risks across touched files
  • Generate concise, actionable review drafts or issue comments to accelerate merges

Quick Start

Ask Claude to review PR <number> by saying review pr <number> to start a structured analysis

Frequently Asked Questions about pr

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

FAQPage Schema
How do I review a pull request for code quality and architecture issues?▼

To review a pull request, analyze the PR metadata, diffs, and discussion history to assess code quality, architecture, and test coverage against project standards. This surfaces concrete file-level concerns, scope creep, and potential risks.

What is the best way to check test coverage in a PR diff before merging?▼

Checking test coverage in a PR diff involves analyzing touched files to detect unresolved questions and assess testing issues against project standards. This generates an actionable review draft with recommended next steps for faster merges.

How do I generate an actionable code review draft from PR discussion history?▼

Generate an actionable code review draft by operating on PR discussion history and diffs to surface issues and risks across files. This provides a structured review with concrete file-level concerns to accelerate merges.

Can I detect scope creep and potential risks across touched files in a pull request?▼

Yes, detecting scope creep and potential risks across touched files in a pull request is possible by analyzing PR metadata and diffs systematically. This surfaces architecture and quality concerns, enabling faster, higher-quality merges.

What should a structured PR review include to surface unresolved questions?▼

A structured PR review should include analysis of PR metadata, discussion history, and diffs to surface unresolved questions and potential risks. This results in concrete file-level concerns and recommended next steps for an actionable review draft.

Related Skills

Explore More Software Engineering Skills→
SuniljitSuniljit

pr-review

Fetch pull request metadata and diffs to generate a structured review.

Community
Intermediate
basilebongbasilebong
1

pr-comment-analyzer

Classify GitHub or GitLab review comments as actionable, non-actionable, or ambiguous.

Community
Advanced
KimjimanKimjiman

verification-loop

Run build, type, lint, test, security, and diff checks before pull requests.

Community
Advanced
roanbrasilroanbrasil
5

static-analysis

Automate static analysis for Java, Kotlin, Python, and Rust codebases.

Community
Advanced