v0.3.0

You can now ask a tour about the step you are reading, and diagrams are drawn by the tool instead of the LLM.

What changed

• Ask about a step. Press ? to pick one of the questions the tour expects at that step, or type your own. The LLM answers from the same files the tour was written from, and the answer becomes the next step. For a tour that tour generated, answers are saved with it. For a tour file you open, they last until you quit.
• Diagrams drawn by the tool. The LLM describes a flow, a timeline or the map of changed files, and tour draws it. Shapes and colors stay the same from tour to tour, and changed and new parts stand out. Notes on code are attached to the line they talk about.
• Easier to read on the screen. Long lines of code wrap instead of being cut off. Tables and code too wide for the right column move below at full width. Flows that start separately, such as a timer job next to a request, are kept apart.
• Judgments grounded in the repository. The LLM now gets the senior engineers' lessons as reference files. A finding is marked "must fix" only when the tour can show an input from this repository that breaks it, and code the repository controls is checked before a problem is blamed on an outside service. In blind reviews on changes the prompts were not tuned on, the average score went from 3.94 to 4.38 out of 5.
• New example tours and demo GIFs.

Tours you saved with v0.2.0 are written again the next time you open the same change, because the prompts changed. With Claude Code, one tour now uses the equivalent of about $1.10 to $1.50 at API prices, a little more than before, because the LLM reads the lessons too.

Install or update

curl -fsSL https://raw.githubusercontent.com/init-co-jp/diff-tour/main/install.sh | sh

v0.2.0

Tours now read a change the way experienced engineers do, not just through a few fixed checks.

What changed

• The senior view is rebuilt from what experienced engineers have written down about reading and reviewing code. A tour now covers three layers: how they read the change, what they ask (eight areas, such as whether the change keeps the old code's promises, what happens when something fails, trust boundaries, and what the tests prove), and how they judge it (how serious each finding is, and what is fine).
• Every finding is listed with its weight (must fix, suggestion, nit, or a question to ask). Only the few that matter most get several steps.
• Suggested fixes are checked against concrete values, so a tour does not recommend a fix that would not prevent the problem.
• When a change is good, the tour says why instead of inventing problems.
• New example tours and demo GIFs written with these prompts.

Tours you saved with v0.1.0 are written again the next time you open the same change, because the prompts changed.

In blind reviews on changes the prompts were not tuned on, tours scored 4.5 out of 5 on average, against 3.5 for v0.1.0. The setup and its limits are in experiments/generate.

Install or update

curl -fsSL https://raw.githubusercontent.com/init-co-jp/diff-tour/main/install.sh | sh

v0.1.0

The first release of diff-tour: walk through a diff the way a senior engineer reads it.

tour turns a git change into a guided tour you step through with → and ←. The tour is written by an LLM you already use, with read-only permissions, and the code on screen is always read from git.

What's in it

• Tour a branch, a commit, a range, or your uncommitted changes. tour alone lets you pick, with your current branch selected
• Tours written by Claude Code or Codex CLI. Gemini CLI support is experimental: it has not yet written a full tour with a real Gemini model
• Steps that show code and diffs from git, examples labeled Example, diagrams, database schemas before and after (SQLite migrations), and questions before the answer
• English and Japanese screens
• Saved tours that open again instantly, and can be shared as JSON

Install

curl -fsSL https://raw.githubusercontent.com/init-co-jp/diff-tour/main/install.sh | sh

Other ways, and what the LLM can and cannot do, are in the README.

Not tested yet: macOS sandboxing for Codex CLI, and Windows.