github/read-diff

Generate a structured Markdown diff report for a git ref range.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/f-campana/bifrost --skill github-read-diff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github/read-diff
Source: https://github.com/f-campana/bifrost/tree/main/skills/github/github-read-diff
Command: npx skills add https://github.com/f-campana/bifrost --skill github-read-diff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the guesswork when auditing code changes by producing a structured diff report between two points in a repository's history, saving time for design reviews, audits, and release checks.

Core Features & Use Cases

  • Diff range computation: compares a git ref range (e.g., HEAD~1..HEAD) in a local repo and identifies changed files.
  • Per-file detail: records filename, change type (added, modified, deleted, renamed), and the diff content.
  • Report delivery: writes a deterministic Markdown report to sanctum/00 Inbox/github-read-diff-[YYYY-MM-DD].md.
  • Use case: support design contracts and QA reviews by making changes visible before iteration.

Quick Start

Use the github/read-diff skill by supplying a repo_path and a ref_range to generate the diff report.

Frequently Asked Questions about github/read-diff

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

FAQPage Schema
How do I generate a structured report of git changes between two commits?▼

To generate a structured report of git changes between two commits, provide a local repository path and a ref range like HEAD~1..HEAD. The skill computes the diff and writes a Markdown file recording per-file changes, including filename, change type, and diff content.

What is the best way to compare a git branch range and list modified files?▼

Comparing a git branch range to list modified files is done by diffing the specified ref range in a local repository. The process identifies added, modified, deleted, or renamed files and records their exact diff content in a structured Markdown report.

Can I use a local repository path to audit code changes before a release?▼

Yes, you can use a local repository path to audit code changes before a release. By supplying the repo path and the target ref range, the skill generates a deterministic diff report that makes all per-file modifications visible for design reviews and release checks.

Does the git diff report include the specific change type for each modified file?▼

Yes, the git diff report includes the specific change type for each modified file. It records whether a file was added, modified, deleted, or renamed, alongside the full diff content for every changed file in the generated Markdown report.

How do I get a per-file diff breakdown for a specific commit range?▼

To get a per-file diff breakdown for a specific commit range, input the repository path and the ref range. The skill processes the git history and outputs a Markdown file detailing every individual file change and its corresponding diff content.