branch-change-explorer

Generates a self-contained interactive HTML page explaining a branch's diff as a navigable file tree.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/bbenefield89/skills --skill branch-change-explorer-bbenefield89
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: branch-change-explorer
Source: https://github.com/bbenefield89/skills/tree/main/skills/branch-change-explorer
Command: npx skills add https://github.com/bbenefield89/skills --skill branch-change-explorer-bbenefield89

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Reviewing a branch or PR diff file-by-file in raw git output makes it hard to grasp the overall goal and the rationale behind each change. This Skill turns the current branch's diff into one offline HTML page with a goal/implemented overview and per-file explanations. ## Core Features & Use Cases - Branch-level overview: Writes goal and implemented-result bullet summaries grounded in the actual diff, ticket, and commit context. - Interactive file tree: Renders a collapsible tree of changed files with added/modified/deleted badges and keyboard navigation. - Per-file explanations: Each file gets a summary, a why rationale, and language-agnostic pseudocode with syntax highlighting. - Use Case: Before a code review, run this Skill on your feature branch to produce a single file:// HTML artifact you can share with reviewers so they understand intent without reading raw diffs. ## Quick Start Ask the assistant to visualize the current branch's changes as an interactive HTML file tree compared against the main branch.

Frequently Asked Questions about branch-change-explorer

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

FAQPage Schema
How do I visualize a git branch diff as an HTML file tree?

Run this Skill on your branch and it diffs against the detected base branch, then renders a self-contained HTML page with a collapsible file tree, per-file summaries, rationale, and pseudocode. The output opens offline from a file:// link.

How does the skill choose the base branch for the diff?

It prefers the repository default from origin/HEAD, then falls back in order to origin/main, origin/master, main, and master. If no base is detectable, it asks you for the comparison target instead of guessing.

Does the diff include uncommitted or staged changes?

Yes. The diff range covers the merge base through the working tree, including staged and unstaged changes, so mid-review working trees are captured. Staged-but-uncommitted work can be diffed against HEAD.

Does the generated HTML page need an internet connection?

No. All CSS and JavaScript are inlined into a single HTML file with zero external dependencies, so it opens offline directly from a file:// link saved to the OS temp directory.

What happens with very large diffs?

For very large diffs the Skill offers to scope the output to a subtree or a subset of paths before writing every file's explanation, keeping the artifact readable and grounded in actual hunks.