diffity-diff

Opens the diffity diff viewer in a browser for Git repository changes.

739|50|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/nilbuild/diffity --skill diffity-diff-nilbuild
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diffity-diff
Source: https://github.com/nilbuild/diffity/tree/main/packages/skills/diffity-diff
Command: npx skills add https://github.com/nilbuild/diffity --skill diffity-diff-nilbuild

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Opens the diffity diff viewer in the browser to visualize changes in a Git repository, enabling rapid review of diffs across commits, branches, and working trees.

Core Features & Use Cases

  • Open the diff viewer directly from a repository to inspect uncommitted changes and historical diffs
  • Compare branches, commits, and PRs in a browser-based UI for quick collaboration and feedback
  • Use case: A developer wants to review a feature branch against main without leaving the terminal

Quick Start

Run diffity in your git repository to launch the browser-based diff viewer.

Frequently Asked Questions about diffity-diff

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

FAQPage Schema
How do I open a git diff in my browser to review code changes?

You can visualize git changes in a browser by launching a local diff viewer server for your repository. This opens a web UI to inspect uncommitted changes and historical diffs across commits, branches, and PRs.

Can I review uncommitted git changes from the terminal without a dedicated GUI?

Yes, running a browser-based diff viewer from your repository opens uncommitted changes in a web UI. It starts a background server if needed and provides a URL to inspect working tree changes without a dedicated desktop GUI.

Do I need to install any binaries to visualize git diffs in a browser?

Yes, visualizing git diffs in a browser requires the diff viewer binary to be installed locally. Once installed, it manages background server startup, reuses existing repository sessions, and outputs the access URL for review.

What is the best way to compare feature branches against main for code review?

Using a browser-based diff viewer is an effective way to compare feature branches against main. It visualizes branch and commit diffs in a web UI, enabling quick collaboration and feedback directly from your local or remote repositories.

How does a browser-based diff viewer handle existing sessions for the same repository?

When visualizing repository changes, the diff viewer reuses an existing session for the same repository instead of starting a new background server. This efficiently manages local resources and immediately prints the active access URL for review.