walkthrough

Generates a narrated, chapter-based visual timeline explaining a diff, branch, PR, or feature.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/muselesscreator/ui-skills --skill walkthrough-muselesscreator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: walkthrough
Source: https://github.com/muselesscreator/ui-skills/tree/main/walkthrough
Command: npx skills add https://github.com/muselesscreator/ui-skills --skill walkthrough-muselesscreator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a large diff or understanding an unfamiliar feature means piecing together scattered files, commit messages, and plans by hand. This Skill turns a diff, branch, PR, or existing feature into a guided story — what changed, why, and how the pieces connect — with real code attached automatically and every touched file accounted for. ## Core Features & Use Cases - Narrative timeline generation: Groups changed files into ordered chapters (data → logic → integration → UI → tests) with plain-language explanations of the why behind each change. - Automatic code attachment: Real diffs (or current file content in feature-tour mode) are captured verbatim and rendered per chapter — never hand-transcribed — with optional focus ranges to highlight key lines. - Plan alignment and completeness checks: Compares the change against any plan or handoff on file, flags deviations and risks, and guarantees every touched file appears in the walkthrough via an automated coverage sweep. - Use Case: Before approving a teammate's 14-file PR, run the walkthrough to get a chat summary plus a published HTML timeline showing each chapter's narrative alongside its real diff, with a coverage badge confirming no file was hidden. ## Quick Start Ask the assistant to walk you through the current branch's diff or a specific PR, for example: walk me through PR 123.

Frequently Asked Questions about walkthrough

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get a guided explanation of a git diff or pull request?▼

Run the walkthrough with a commit range, PR number, or no argument to default to the current branch's diff against the base branch. It produces a chat summary plus a published HTML timeline with chapters and the real diff attached per file.

Can I use this to explain an existing feature with no pending changes?▼

Yes. When given file or directory paths with no diff against the base branch, it switches to feature-tour mode and narrates the current implementation instead, attaching real file content rather than a diff.

Does the walkthrough check changes against a plan or handoff?▼

Yes. It looks for plan and handoff files from prior sessions, plus open decision memos, and adds a Plan Coverage section and deviation, undocumented, or tradeoff flags when the code diverges from what was planned.

What happens if some changed files are left out of the walkthrough?▼

The render step independently compares the authoritative changed-file list against every path referenced in the walkthrough. Missed files are swept into an auto-generated Unplaced files section with their diffs, and the coverage badge turns amber.

When should I not use a walkthrough for code questions?▼

Skip it for single targeted questions about one behavior or line — a direct Q&A tool fits better. The walkthrough is built for narrating a whole diff, branch, PR, or feature as a connected story, not isolated lookups.