pr-change-analyzer

Analyze PR commit history and structure using git commands.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/yegecali/custom-copilot --skill pr-change-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-change-analyzer
Source: https://github.com/yegecali/custom-copilot/tree/main/Java-Backend/.github/skills/pr-change-analyzer
Command: npx skills add https://github.com/yegecali/custom-copilot --skill pr-change-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the review of Pull Request (PR) commit quality, ensuring adherence to best practices and identifying potential issues before merging.

Core Features & Use Cases

  • Commit Structure Analysis: Validates Conventional Commits, analyzes commit granularity, and assesses file distribution.
  • Risk Assessment: Calculates a risk score for each commit and the overall PR based on size, complexity, and adherence to standards.
  • Use Case: Before merging a feature branch, run this Skill to get an automated report on commit quality, ensuring consistency and reducing the burden on human reviewers.

Quick Start

Use the pr-change-analyzer skill to analyze the last 10 commits in the current branch.

Frequently Asked Questions about pr-change-analyzer

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

FAQPage Schema
How do I analyze pull request commit quality automatically?

PR quality analysis calculates a risk score for each commit by evaluating size, complexity, and adherence to Conventional Commits standards. It assesses commit granularity, file distribution, and structural compliance to identify potential issues before merging.

How do I check if my git commits follow Conventional Commits standards?

Checking Conventional Commits compliance involves validating commit history and structure using git commands. The analysis evaluates commit messages against established coding standards to ensure consistency and reduce the burden on human reviewers before merging.

Can I assess PR risk score based on git diff-tree output?

Yes, you can assess PR risk score based on git diff-tree output. The analysis uses git diff-tree to gather detailed commit statistics and calculates a risk score for each commit and the overall PR based on size, complexity, and standard adherence.

What is the best way to review commit granularity in a feature branch?

The best way to review commit granularity in a feature branch is to automate commit structure analysis. By evaluating the distribution of changes across files and validating commit size, you can ensure appropriate granularity before merging.

Do I need to run git log manually for PR analysis?

No, you do not need to run git log manually for PR analysis if you use an automated skill. The automation requires the execution of git log and git diff-tree commands internally to gather detailed commit statistics and validate adherence to coding standards.