pr-analysis

Parse GitHub pull request data and summarize metadata, diffs, and scope.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/maverox/claude-plugins --skill pr-analysis-maverox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-analysis
Source: https://github.com/maverox/claude-plugins/tree/main/plugins/connector-integration-suite/skills/pr-analysis
Command: npx skills add https://github.com/maverox/claude-plugins --skill pr-analysis-maverox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fetch and analyze pull request data from GitHub to provide structured PR metadata, file-change insights, and change-scope identification, reducing manual PR review time.

Core Features & Use Cases

  • Retrieve PR metadata: number, title, author, state, and timestamps.
  • List changed files and categorize them by area (connectors, core domain, tests, docs).
  • Generate a diff summary and identify scope of changes for downstream skills like code-quality-review or integration validators.
  • Auto-activation for common requests like 'analyze PR', 'get PR details', or 'what changed in this PR'.

Quick Start

Ask me to analyze PR #123 in repository owner/repo to generate a detailed PR report.

Frequently Asked Questions about pr-analysis

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

FAQPage Schema
How do I get a summary of changed files and metadata for a GitHub pull request?

Pull request analysis parses PR metadata, file changes, and commit history via the gh CLI to categorize changes into connectors, core domain, tests, and docs, reducing manual review time.

Can I analyze a GitHub pull request without manually specifying the repository owner and name?

Yes, pull request analysis supports repository auto-detection. You can simply provide the PR number or URL, and the tool will automatically identify the target repository to fetch the necessary metadata and diffs.

Does pull request analysis work with the GitHub CLI to fetch commit history and file diffs?

Yes, pull request analysis leverages the GitHub CLI to fetch PR metadata, file changes, and commit history to generate a structured diff summary.

What is the best way to categorize file changes in a pull request by scope?

The best way to categorize file changes by scope is to parse the PR diff and group modified files into connectors, core domain, tests, and docs for structured review.

How to prepare pull request data for downstream code quality review or integration validation?

To prepare pull request data for downstream review, generate a diff summary and identify the change scope to provide structured metadata for skills like code-quality-review or integration validators.