analyse-pr

Analyze pull requests and generate structured analysis and feedback reports.

13|2|Updated Nov 16, 2025
One-click install
npx skills add https://github.com/rstacruz/agentic-toolkit --skill analyse-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyse-pr
Source: https://github.com/rstacruz/agentic-toolkit/tree/main/skill/atk/analyse-pr
Command: npx skills add https://github.com/rstacruz/agentic-toolkit --skill analyse-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzing pull requests is time-consuming and error-prone. This skill helps engineers quickly extract key changes, detect potential issues, and generate structured, actionable feedback.

Core Features & Use Cases

  • PR analysis: automatically summarize changes, risk areas, and impacted components.
  • Feedback generation: produce targeted, prioritized feedback for code owners.
  • Artefact storage: save analysis and feedback reports to artefacts/pr_{number}analysis.md and artefacts/pr{number}_feedback.md.
  • Inline output option: optionally output results inline without saving documents.

Quick Start

Analyse a PR to generate both a detailed analysis and a feedback report.

Frequently Asked Questions about analyse-pr

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

FAQPage Schema
How do I automate pull request analysis and generate code review feedback?

Automate pull request analysis by processing diffs, metadata, and dependency changes to extract risk areas and generate structured, prioritized feedback. This skill produces actionable insights for code owners and supports both full reports and inline outputs.

What is the best way to summarize code changes and detect risks in complex pull requests?

Summarize code changes and detect risks by analyzing diffs and dependency changes across codebases. The analysis identifies impacted components and risk areas, outputting a structured report to artefacts/pr_{number}_analysis.md in your working directory.

Can I generate inline PR feedback without saving markdown files to my working directory?

Generate inline PR feedback without saving files by using the inline output option. By default, the skill saves a feedback report to artefacts/pr_{number}_feedback.md, but you can opt to output results directly inline instead.

Does PR analysis work with dependency changes and metadata, or just code diffs?

PR analysis works with dependency changes, metadata, and code diffs. It applies to typical and complex pull requests across codebases, ensuring a comprehensive review that goes beyond just the code diff to include structural dependencies.

How do I save structured PR analysis and feedback reports as artefacts?

Save structured PR analysis and feedback reports automatically to the artefacts directory. The skill generates pr_{number}_analysis.md for the change summary and pr_{number}_feedback.md for the prioritized feedback directly in your working directory.

What limitations are there when using automated code review for large pull requests?

Automated code review for large pull requests handles complex diffs and dependency changes but requires reviewing the generated artefacts for context. While it extracts impacted components and risk areas, human validation of prioritized feedback remains necessary for nuanced architectural decisions.