Analyze PR

Evaluate GitHub pull requests for completeness, evidence, and risk.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/softbreezee/claw-os --skill analyze-pr-softbreezee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Analyze PR
Source: https://github.com/softbreezee/claw-os/tree/main/temp_stock_skills/daily_stock_analysis-main/.claude/skills/analyze-pr
Command: npx skills add https://github.com/softbreezee/claw-os --skill analyze-pr-softbreezee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes GitHub Pull Requests to assess necessity, description completeness, evidence, major risks, and whether changes can be merged directly.

Core Features & Use Cases

  • Automated PR metadata checks: validates presence of PR type, background/problem, scope, issue link, verification commands, compatibility, and rollback plans against the repository template.
  • Evidence-driven review: gathers CI results, PR checks, and diff information to inform risk and acceptance criteria.
  • Review generation: produces a structured PR analysis report suitable for documentation and team reviews.

Quick Start

Provide a PR number to the analyze-pr tool to generate a structured PR review.

Frequently Asked Questions about Analyze PR

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

FAQPage Schema
How do I automate GitHub pull request reviews for CI evidence and risk assessment?

Automating GitHub pull request reviews involves parsing PR metadata, diffs, and CI status to validate template completeness and assess risks. The tool analyzes CI evidence and repository guidelines to produce a structured PR assessment with actionable merge recommendations.

What is included in a structured pull request analysis report?

A structured pull request analysis report includes validation of PR type, background, scope, and issue links against templates. It evaluates CI results, verifies evidence, identifies major risks, and provides clear acceptance criteria alongside merge recommendations.

How do I check if a pull request follows the repository template before merging?

Checking PR template compliance requires validating the presence of background, problem scope, verification commands, compatibility, and rollback plans. The tool automates template checks by parsing PR data against repository guidelines to ensure documentation completeness.

Can I assess pull request merge risks using CI results and diff information?

Assessing PR merge risks using CI results and diffs is possible by gathering CI checks and diff information to inform acceptance criteria. The tool parses CI status and code changes to evaluate evidence and produce risk-based merge recommendations.

What do I need to generate a structured PR review for my team?

Generating a structured PR review requires providing a PR number to the analysis tool. The Skill then parses PR metadata, diffs, CI evidence, and repository guidelines to produce an assessment suitable for team reviews and documentation.

When should I use automated PR analysis instead of manual code review?

Automated PR analysis is ideal for projects requiring standardized review templates, CI evidence, and clear acceptance criteria. It streamlines evaluation of completeness and risk, though manual review remains valuable for complex logic and architectural decisions.