fetch-diff

Fetch GitHub pull request diffs with line numbers and file filtering.

1|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/bossjones/boss-skills --skill fetch-diff-bossjones
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fetch-diff
Source: https://github.com/bossjones/boss-skills/tree/main/plugins/boss-dev/agent-harness/skills/fetch-diff
Command: npx skills add https://github.com/bossjones/boss-skills --skill fetch-diff-bossjones

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires aiohttp, pydantic, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of fetching GitHub pull request diffs with line numbers and filtering, streamlining code review workflows.

Core Features & Use Cases

  • Annotated PR Diffs: Fetches PR diffs from GitHub with line numbers for easier review-comment placement.
  • File Filtering: Filters PR diffs by file patterns to focus on specific code sections.
  • Auto-generated and Deleted Files: Masks auto-generated files and deleted files to maintain focus on hand-written code changes.
  • Use Case: For developers who need to quickly review and comment on pull requests, this Skill automates the generation of annotated diffs for efficient code review.

Quick Start

Use the fetch-diff skill to fetch the diff for a PR at 'https://github.com/owner/repo/pull/123'.

Frequently Asked Questions about fetch-diff

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

FAQPage Schema
How do I fetch a GitHub pull request diff with line numbers for code review?

Fetching a GitHub pull request diff with line numbers requires accessing the GitHub API to retrieve and annotate PR data. This Skill automates that process, providing annotated diffs so developers can efficiently map review comments to specific lines.

Can I filter a PR diff by file patterns to focus on specific code sections?

Yes, you can filter a PR diff by specific file patterns to focus your code review on targeted sections. This allows developers to isolate relevant code changes while automatically masking auto-generated and deleted files to reduce noise.

Do I need GitHub API authentication to automate fetching PR diffs?

Yes, GitHub API authentication is required to fetch PR diffs automatically. You must configure environment variables with your GitHub credentials so the tool can securely access repository data and retrieve the annotated pull request diffs.

What is the best way to automate code review for auto-generated files in pull requests?

The best way to handle auto-generated files during code review is to use a diff fetching tool that automatically masks them. This approach maintains focus on hand-written code changes, reducing noise and streamlining the review workflow.

How does masking deleted files in a PR diff improve code review?

Masking deleted files in a PR diff improves code review by hiding irrelevant removed content from the display. This keeps the reviewer's focus strictly on active, hand-written code modifications, making the automated review process more efficient.