pr-reference

Generate structured XML documents of commit history and diffs between branches.

2|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/kfolkes/dotnet-modernization-db-transform --skill pr-reference
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-reference
Source: https://github.com/kfolkes/dotnet-modernization-db-transform/tree/main/hve-core/.github/skills/shared/pr-reference
Command: npx skills add https://github.com/kfolkes/dotnet-modernization-db-transform --skill pr-reference

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of gathering detailed information about code changes between branches, essential for creating comprehensive pull request descriptions and facilitating code reviews.

Core Features & Use Cases

  • PR Description Generation: Automatically create detailed descriptions for pull requests based on commit history and unified diffs.
  • Code Review Assistance: Provide reviewers with structured context of changes, including commit metadata and diff content.
  • Branch Analysis: Analyze differences between branches to understand the scope of changes, discover work items, or perform security analysis on modified files.
  • Structured Diff Summaries: Generate XML output that can be programmatically parsed for various reporting needs.

Quick Start

Generate a PR reference XML file comparing the current branch against origin/main.

Frequently Asked Questions about pr-reference

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

FAQPage Schema
How do I generate a pull request description from git commit history and diffs?

You can generate a pull request description by running git commands to extract commit history and unified diffs between branches, compiling them into a structured XML document that serves as a detailed PR reference. Both bash and PowerShell implementations are provided.

Can I get a structured XML diff output for branch change analysis?

Yes, you can generate structured XML diff output for branch analysis. The Skill captures unified diffs and commit metadata between branches into an XML format that can be programmatically parsed to discover work items or perform modified file security analysis.

Does this code review tool require git installed on my system?

Yes, this code review preparation tool requires git to be available on your system PATH. It relies on git commands to list changed files, read diff chunks, and gather the commit history necessary for structured code review context.

What is the best way to list changed files between branches for code review preparation?

The best way to list changed files for code review preparation is using the Skill's built-in utilities, which execute git commands to identify modified files and read diff chunks between branches, providing structured context of all changes.

Does the git diff XML generation work on both Windows and Linux environments?

Yes, the git diff XML generation works on both Windows and Linux environments because it includes dual implementations. It provides both bash and PowerShell scripts to ensure cross-platform shell compatibility when running git commands.