pr-diff

Diff the current branch against a target branch to surface PR changes.

Updated Dec 3, 2025
One-click install
npx skills add https://github.com/idodoron11/Agentarium --skill pr-diff-idodoron11
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-diff
Source: https://github.com/idodoron11/Agentarium/tree/main/skills/pr-diff
Command: npx skills add https://github.com/idodoron11/Agentarium --skill pr-diff-idodoron11

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) components.

What problem does it solve?

Produces a structured diff between the current branch and a target branch, giving the agent full context on what the PR introduces.

Core Features & Use Cases

  • PR review: User asks to review or audit PR changes
  • PR summarization: User wants a PR title and description drafted from the diff
  • Create PR: User asks to open or create a new PR with a generated title and description
  • User wants to understand what files were modified before a code review
  • Show the diff, "what changed", or compare to main/master

Quick Start

Provide a target branch when prompted and run the corresponding diff script to generate the PR context.

Frequently Asked Questions about pr-diff

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

FAQPage Schema
How do I generate a pull request diff from a git branch?

To generate a pull request diff, you provide a target branch and the Skill computes the differences against your current branch. It outputs a structured diff along with metadata like modified files and branch names to drive PR workflows.

Can I summarize code changes before creating a pull request?

Yes, you can summarize code changes by computing the diff against a target branch. The skill surfaces modified files and diff size, allowing you to draft a PR title and description directly from the generated context.

What is needed to compare my current branch against a main repository branch?

Comparing your current branch against a target branch requires Git installed in your environment. You must provide the target branch name when prompted so the script can execute the diff computation and list the modified files.

Does this PR review tool show which files were modified in a Git repository?

Yes, the PR review tool explicitly lists modified files by computing a diff between your current branch and a specified target branch. It exposes this file list along with the overall diff size to help you audit changes before review.

What is the best way to draft a pull request description from a code diff?

The best way to draft a pull request description is to compute a structured diff between your current and target branches. This provides the agent with full context on what the PR introduces, enabling automated title and description generation.

When should I avoid using an automated branch diff for code review?

You should avoid using an automated branch diff if your repository lacks a Git environment or if you cannot specify a target branch. The tool requires a target branch to compute differences and surface modified files for review.