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