# Walkthroughs

# Walkthroughs

A big PR is hard to read top-to-bottom. A **walkthrough** is a hosted, guided tour of the change that inline builds automatically: the diff reorganized into an ordered sequence of coherent layers, with diagrams, a visual recap of what changed for users, and a chat to ask questions — all on a page you can share by link.

## What it contains

- **Layers.** Instead of alphabetical files, the PR is grouped into 2–6 cohesive change cohorts, ordered so you can read them as a story, each with its file ranges and a Mermaid diagram where useful.
- **Visual recap.** For UI and API changes, before/after wireframes and data-model / endpoint cards summarizing the user-facing impact.
- **Ask inline.** A streaming chat scoped to the PR's diff, so a reviewer can ask "why was this changed?" without leaving the page.

## How it's built

inline builds the walkthrough in two passes powered by a fast model: one reorganizes the PR into ordered layers with diagrams, another produces the visual recap. The diff is then **frozen** into the walkthrough record, so the public page renders without any GitHub call. The placeholder in inline's PR comment is swapped for a signed link when the build finishes.

## Where it lives

- **Public viewer** — `/w/<token>`. The share token is the credential; the page is `noindex`. Anyone with the link can read it, no account needed.
- **Portal twin** — **Reviews → (review) → Walkthrough**, org-scoped, which also exposes GitHub actions.

The "Ask inline" chat is answered by Claude with a large diff budget and tight rate limits.

## Enabling

Off by default. Turn on **Walkthroughs** in [review config](./review-config.html) (per-repo over workspace). Each walkthrough records its own cost like any other AI artifact.