pr-reference
Generates PR reference XML with commit history and unified diffs between branches, with extension and path filtering. Use when creating pull request descriptions, preparing code reviews, analyzing branch changes, discovering work items from diffs, or generating structured diff summaries.
Works with
--- name: pr-reference description: Generates PR reference XML with commit history and unified diffs between branches, with extension and path filtering. Use when creating pull request descriptions, preparing code reviews, analyzing branch changes, discovering work items from diffs, or generating structured diff summaries. license: MIT --- # PR Reference Generation Skill ## Overview Queries git for commit metadata and diff output, then produces a structured XML document. Both bash and PowerShell implementations are provided. Use cases: * PR description generation from commit history * Code review preparation with structured diff context * Work item discovery by analyzing branch changes * Security analysis of modified files After successful generation, include a file link to the absolute path of the XML output in the response. ## Prerequisites The repository must have at least one commit diverging from the base branch. | Platform | Runtime | |----------------|----------------------| | macOS / Linux | Bash (pre-installed) | | Windows | PowerShell 7+ (pwsh) | | Cross-platform | PowerShell 7+ (pwsh) | ## Quick Start Run the following command to generate a PR reference with default settings (compares against `origin/main`): ```bash scripts/generate.sh scripts/generate.sh --base-branch auto --merge-base --exclude-ext yml,json ``` ```powershell scripts/generate.ps1 scripts/generate.ps1 -BaseBranch auto -MergeBase -ExcludeExt yml,json ``` Output saves to `.copilot-tracking/pr/pr-reference.xml` by default. ## Parameters Reference | Parameter | Flag (bash) | Flag (PowerShell) | Default | Description | |--------------------|------------------|------------------------|--------------------------------------------|--------------------------------------------------------------------| | Base branch | `--base-branch` | `-BaseBranch` | `origin/main` (bash) / `main` (PowerShell) | Target branch for comparison. Use `auto` to detect remote default. | | Merge base | `--merge-base` | `-MergeBase` | false | Use `git merge-base` for three-way comparison | | Exclude markdown | `--no-md-diff` | `-ExcludeMarkdownDiff` | false | Exclude markdown files (*.md) from the diff | | Exclude extensions | `--exclude-ext` | `-ExcludeExt` | (none) | Comma-separated extensions to exclude (e.g., `yml,yaml,json,png`) | | Exclude paths | `--exclude-path` | `-ExcludePath` | (none) | Comma-separated path prefixes to exclude (e.g., `docs/,.github/`) | | Output path | `--output` | `-OutputPath` | `.copilot-tracking/pr/pr-reference.xml` | Custom output file path | Both defaults resolve to the same remote comparison. The PowerShell script automatically resolves `origin/<branch>` when a bare branch name is provided. ## Additional Scripts Reference After generating the PR reference, use these utility scripts to query the XML. ### List Changed Files Run the list script to extract file paths from the diff: ```bash scripts/list-changed-files.sh # all changed files scripts/list-changed-files.sh --type added # filter by single type scripts/list-changed-files.sh --type added,modified,renamed # filter by multiple types scripts/list-changed-files.sh --exclude-type deleted # exclude specific types scripts/list-changed-files.sh --format markdown # output as markdown table ``` ```powershell scripts/list-changed-files.ps1 # all changed files scripts/list-changed-files.ps1 -Type Added # filter by single type scripts/list-changed-files.ps1 -Type Added,Modified,Renamed # filter by multiple types scripts/list-changed-files.ps1 -ExcludeType Deleted # exclude specific types scripts/list-changed-files.ps1 -Format Json # output as JSON ``` | Parameter | Flag (bash) | Flag (PowerShell) | Default | Description | |--------------|------------------|-------------------|---------|-----------------------------------------------------------------------| | Input path | `--input`, `-i` | `-InputPath` | (auto) | Path to pr-reference.xml | | Type filter | `--type`, `-t` | `-Type` | `all` | Change types to include (comma-separated: added, modified, etc.) | | Exclude type | `--exclude-type` | `-ExcludeType` | (none) | Change types to exclude. Mutually exclusive with `--type` (non-`all`) | | Format | `--format`, `-f` | `-Format` | `plain` | Output format: plain, json, or markdown | ### Read Diff Content Run the read script to inspect diff content with chunking for large diffs: ```bash scripts/read-diff.sh --info # chunk info (count, line ranges) scripts/read-diff.sh --chunk 1 # read a specific chunk scripts/read-diff.sh --file src/main.ts # extract diff for one file scripts/read-diff.sh --summary # file stats summary ``` ```powershell scripts/read-diff.ps1 -Info # chunk info scripts/read-diff.ps1 -Chunk 1 # read a specific chunk scripts/read-diff.ps1 -File "src/main.ts" # extract diff for one file ``` ## Output Format The generated XML wraps commit metadata and unified diff output in a `<commit_history>` root element. See the [reference guide](references/REFERENCE.md) for the complete XML schema, element reference, output path variations, and workflow integration patterns. ## Troubleshooting | Symptom | Cause | Resolution | |---------------------------------|---------------------------------------|---------------------------------------------------------------------------| | "No commits found" or empty XML | No diverging commits from base branch | Verify the branch has commits ahead of the base with `git log base..HEAD` | | "Branch not found" error | Base branch ref missing locally | Run `git fetch origin` to update remote tracking refs | | "git: command not found" | git is not on PATH | Install git or verify PATH includes the git binary directory |
More Code Review skills
pr-to-video
heygen-com/hyperframes
Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.
receiving-code-review
obra/superpowers
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
public-relations
coreyhaines31/marketingskills
When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'public relations,' 'press,' 'press release,' 'press coverage,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'Help A Reporter,' 'reporter request,' 'tech press,' 'TechCrunch,' 'earned media,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' 'podcast prep,' 'going on a podcast,' 'podcast guest,' 'prep me for this podcast,' or 'how do I get press.' Use this for earned media work — finding journalists, pitching stories, newsjacking, prepping podcast appearances, and responding to press requests. For startup/SaaS/AI directory submissions, see directory-submissions. For product launches, see launch. For social-media engagement, see social. For cold-email outreach to prospects, see cold-email.

