Slide types, JSON shapes, and storytelling rules for explaining code changes. Read once before building a deck.

List changed files (status, churn) and their numbered changes (contiguous blocks of added/removed/re-indented lines) with previews. Change numbers match diff slides with a git source: assign them to steps with steps[].changes.

Create an empty presentation deck. Returns its id and live viewer URL. Add content with add_slides.

Append slides to a deck (or insert after a slide id). Returns the outline and any warnings (unmatched callouts, unknown ids). Changes appear live in an open viewer. See authoring_guide for slide types.

Replace one slide with a new definition (send the complete slide). Keeps its id and position.

Remove slides by id.

Set the slide order. Ids you omit keep their relative order after the listed ones.

Change deck metadata or theme.

Return the deck outline and the authoring JSON of its slides (or one slide), e.g. to edit with update_slide.

List saved decks, newest first.

Permanently delete a deck, its change plan and its viewer chat. Only do this when the user asks: it cannot be undone.

Create a skeleton deck from a git range: title with stats, a file map, and one stepped diff slide per significant file (one step per hunk). Then refine: add narration, callouts, behavior slides, and a review checklist with update_slide/add_slides.

Open the deck in the user's browser (live: later edits appear immediately). Returns the URL.

Write the deck as one self-contained HTML file (viewer, fonts, and code inlined) to share or attach to a PR.

Wait until the user sends a change plan from the viewer's feedback panel (C key), then return it: code changes they want in the repository the deck explains, each with the slide, step and pinned element (often a code line) it was written on, plus the slide's authoring JSON. Returns at once if requests are already pending. The viewer shows the user that you are listening. Make the changes in the code (not the slides), resolve_feedback, then call this again to keep reviewing together.

Return the pending change plan left in the viewer (without waiting) and mark it as being worked on: code changes to make in the repository the deck explains. Use when the user says they left feedback.

Close change requests after making the code changes (or declining them). Each reply appears in the viewer next to the request.

Post a message in the viewer chat without closing anything: ask a clarifying question about a request (by id), or say something about the whole deck (no id). The user answers in the viewer; wait_for_feedback returns their answer.