What problem does it solve? Understanding a large branch, pull request, or commit range by reading raw git diff output is slow and error-prone, especially when changes span many files, renames, binaries, and multiple commits. This Skill turns any changeset into a structured, neutral explanation with verbatim hunks and interactive navigation. ## Core Features & Use Cases - Three Context Modes: Explain a specific commit or range, a pull/merge request (including fork PRs), or a branch compared against its merge base using a shared branch resolver. - Tri-Lens Walkthroughs: Navigate the changeset by semantic topic clusters, by individual file, or commit-by-commit, with drill-down Q&A on callers, prior behavior via git log/blame, and related hunks. - Rigorous Diff Accounting: Reconciles hunk counts, line additions/deletions, renames, copies, binaries, submodules, symlinks, and mode changes against numstat output so no change is silently dropped. - Use Case: A reviewer opens a 12-commit PR touching 40 files and asks for an explanation; the Skill produces an overall summary with a commit timeline, clusters hunks into functional topics, and lets the reviewer step through each topic with verbatim diff hunks. ## Quick Start Explain the changes on my current branch compared to main, starting with an overall summary and then walking me through it topic by topic.