What problem does it solve? Raw git diffs show which lines changed but not why, making it hard to understand a PR, branch, or commit as a coherent set of features spread across many files. ## Core Features & Use Cases - Concept-level explanation: Identifies the two to five features a change is made of and traces each one across every file and hunk it touches, rather than walking file by file. - Rich HTML output: Produces a single self-contained HTML file with inline CSS, hand-applied syntax highlighting, colored diff hunks, diagrams, and callouts, saved to a gitignored location with a date-prefixed filename. - Flexible diff sources: Resolves the change from a PR number via gh, a branch comparison, a commit range, or the uncommitted working tree. - Use Case: Before merging a teammate's large PR, ask for an explanation and receive a scrolling HTML document with background, intuition, an anatomy of the change, and a code walkthrough organized by concept. ## Quick Start Explain the changes in PR 42 as an HTML document that walks through the concepts and features across all the files it touches.
