git-diff

Name: git-diff
Availability: InStock
Author: theslashdojo

Identify and review exact changes across git states with unified diff output.

Updated Apr 10, 2026

Search Tags:#git #diff #branch #patch #code-review #version-control #unified-diff

Ready to run

npx skills add https://github.com/theslashdojo/dojo --skill git-diff

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-diff
Source: https://github.com/theslashdojo/dojo/tree/main/nodes/git/diff
Command: npx skills add https://github.com/theslashdojo/dojo --skill git-diff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill helps developers see exactly what changed between git states, enabling precise reviews and safe commits.

Core Features & Use Cases

Three-way comparisons across the Working Tree, Index, and HEAD to surface unstaged, staged, and committed changes.
Per-file and per-branch diffs with unified diff output, plus patch generation for sharing changes.
Real-world workflows include reviewing local edits before staging, validating branch merges, and auditing changes between commits.

Quick Start

Compare the working tree with the index to preview unstaged changes before staging.

Frequently Asked Questions about git-diff

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

FAQPage Schema

How do I review unstaged changes in my working tree before staging?▼

Review unstaged changes by comparing the working tree against the index using git diff. This surfaces exact local edits in unified diff format, helping you validate code before staging or committing.

Can I generate a unified diff patch file between two git branches?▼

Yes, you can generate a unified diff patch file between two git branches. Comparing branches outputs the exact per-file differences, enabling safe merge validation and patch generation for sharing changes.

What is the best way to see per-file differences between commits?▼

The best way to see per-file differences between commits is using git diff and git show. This identifies exact changes across git states, outputting unified diff format for precise code review.

Do I need Git installed to compare staged changes against HEAD?▼

Yes, you need Git installed to compare staged changes against HEAD. The skill executes standard repository commands like git diff and git diff --stat to surface exact changes across git states.

How does a three-way comparison across the index and HEAD work for code review?▼

A three-way comparison across the working tree, index, and HEAD surfaces unstaged, staged, and committed changes. This mechanism isolates exact modifications at each git state, informing precise reviews and safe commits.