skills.rest
shopwareLabs
shopwareLabsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

pr-analyzing

Analyze GitHub pull requests by aggregating metadata, diffs, reviews, and comments with architectural context.

41|5|Updated Oct 22, 2025
Search Tags:#research#github#analyze#pull-request#code-research#architectural-context
One-click install
npx skills add https://github.com/shopwareLabs/ai-coding-tools --skill pr-analyzing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-analyzing
Source: https://github.com/shopwareLabs/ai-coding-tools/tree/main/plugins/code-contribution-analysis/skills/pr-analyzing
Command: npx skills add https://github.com/shopwareLabs/ai-coding-tools --skill pr-analyzing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use this skill to analyze a GitHub pull request by combining authoritative PR data with architectural context, delivering a structured analysis of scope, impact, and relationships within the codebase.

Core Features & Use Cases

  • Fetches PR metadata, changed files, diffs, reviews, and comments from GitHub.
  • Performs architectural context research via the chunkhound-integration MCP.
  • Accepts optional triage reasoning from callers to focus research depth and emphasis.

Quick Start

Provide a PR number to analyze, for example Analyze PR #4521, and the skill will fetch data and deliver an architectural review.

Frequently Asked Questions about pr-analyzing

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

FAQPage Schema
How do I analyze a GitHub pull request for architectural impact and scope?▼

You can analyze a PR by providing its number, which prompts the skill to fetch changed files, diffs, reviews, and comments from GitHub, then apply architectural context research to deliver a structured review of scope and impact.

What is the best way to review code changes with architectural context?▼

Reviewing code changes with architectural context requires fetching GitHub PR data like diffs and comments, then cross-referencing it with architectural research to evaluate scope, impact, and codebase relationships.

Does analyzing pull requests require access to GitHub data and MCP integration?▼

Analyzing pull requests requires access to GitHub data for PR metadata and the chunkhound-integration MCP for architectural research to successfully assess scope and impact.

Can I add triage context when analyzing a GitHub PR's impact?▼

You can pass optional triage reasoning from callers when analyzing a GitHub PR to focus research depth and emphasis on specific architectural touchpoints and areas of impact.

What limitations exist when analyzing large pull requests across different components?▼

While the skill handles PRs of varying sizes across different components, its analysis depends on accessing GitHub data and the chunkhound-integration MCP to successfully evaluate architectural touchpoints and impact.

Related Skills

Explore More Software Engineering Skills→
shopwareLabsshopwareLabs
41

issue-analyzing

Analyze GitHub issues with code-context research and structured output.

Official
Advanced
ZaxbyHubZaxbyHub

tech-debt-ci-review

Audits repositories for technical debt, test theater, flaky tests, and CI instability.

Official
Advanced
luicabref97luicabref97

tdd:write-tests

Generate unit and integration tests for unstaged git diffs or the latest commit.

Community
Advanced
jdforsythejdforsythe

wolfe-init

Automate repository bot setup for code review, security scanning, and performance analysis.

Community
Advanced