Guided PR tours

Ask Neon to trace a change and it can turn the answer into an ordered route through the diff. Each stop explains one exact changed-line range, so you can follow the implementation without manually hunting through files and call sites.

Neondeck PR review showing an Ask reviewer question and its seven-step guided tour card — The narrow crop focuses on the reviewer question and step list; the wide-screen overview uses editorial callouts to highlight the question and walkthrough entry points. In the product, the diff annotation, top traversal controls, and reviewer-side step list stay synchronized to one review cursor. Open the full annotated overview.

Ask for a walkthrough

Open Ask reviewer for a completed PR review and send a focused request. You can use natural language or type the reviewer messages directly:

/show-me how authentication reaches the route handler
/tour the new caching flow

Neon starts from the existing review context, investigates the exact reviewed revision with read-only repository tools, and publishes the smallest useful ordered set of anchors. When a navigable tour would not improve the answer, it responds in prose instead.

Reviewer commands: Type / in the reviewer composer to discover /help, /re-review, and /show-me. The /tour alias completes to /show-me. These remain reviewer-scoped messages and actions, not global Neondeck commands.

Walk or read the route

Follow the cursor

Choose Tour in Traverse, use the [/] shortcuts, click a step, or press Previous and Next. Every control moves the same review cursor.

Choose the view

Walk keeps the full diff in view. Read stitches only the anchored ranges together in tour order and keeps a path back to the complete diff.

Stay in context

Ask about the active step, start over, or close and reopen the tour. A follow-up question carries the selected step's exact file and range into the continuing reviewer conversation.

Exact-revision safety

A tour is local Neondeck review state, not a GitHub review artifact. The reviewer proposes a complete route, while the application binds it to the current review and validates every range against visible added or deleted lines in that exact revision.

A tour contains between one and twelve ordered steps.
If any file or line range cannot be validated, publication fails as a whole and the current tour remains unchanged.
Publishing another tour atomically replaces the prior route instead of accumulating conflicting annotations.
Tours never create findings, local draft comments, GitHub comments, or a submitted review.
A tour from an older PR revision is never silently re-anchored onto a newer one.

Start from a finding

A Neon finding can offer Show me why. That request traces the finding's evidence into the same guided-tour experience and adds a return path to the source finding. The finding's severity, draft state, and lifecycle do not change when the tour is published.