glimpse-changes

Render session diffs as a Markdown walkthrough in a native Glimpse window.

883|68|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/saffron-health/libretto --skill glimpse-changes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: glimpse-changes
Source: https://github.com/saffron-health/libretto/tree/main/.agents/skills/glimpse-changes
Command: npx skills add https://github.com/saffron-health/libretto --skill glimpse-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires glimpse-changes.

What problem does it solve?

Plain text diffs in a terminal are hard to review, especially for multi-file changes. This Skill turns the current session diff into a structured, narrative HTML walkthrough with syntax highlighting and rich diff rendering, displayed in a native Glimpse window for easier code review.

Core Features & Use Cases

  • Visual diff walkthroughs: Converts the current git session diff into a single HTML page with prose explanations and focused changes blocks referencing real files and line ranges.
  • Inline and unified diffs: Supports ad-hoc diff fenced blocks with literal +/- lines or pasted unified diff output, plus syntax-highlighted code blocks.
  • User review collection: Blocks until the window is closed, or runs in --background mode writing the user's review feedback to a file for asynchronous workflows.
  • Use Case: After an agent finishes a multi-file refactor, pipe a Markdown walkthrough into npx glimpse-changes so a reviewer sees each change explained in narrative order rather than raw diff order.

Quick Start

Ask the agent to use the glimpse-changes skill to create a visual walkthrough of the current uncommitted changes and open it for review.

Frequently Asked Questions about glimpse-changes

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

FAQPage Schema
How do I visualize a git diff as an HTML page?

Pipe a Markdown document with `changes` fenced blocks listing file paths into `npx glimpse-changes`. The CLI resolves old and new file contents from git automatically and renders a syntax-highlighted walkthrough in a native Glimpse window.

How do I show only part of a file in a diff walkthrough?

Append a line range to the file path inside a `changes` block, such as `src/config.ts:42-50`. The renderer focuses the diff on that range while still resolving content from git.

Can glimpse-changes collect review feedback from the user?

Yes. By default the CLI blocks until the window is closed. With `--background`, it prints a review file path that contains `__PENDING__` until the window closes, then holds the user's review text or a no-review message.

Why is my Markdown output garbled when using a heredoc?

Do not escape backticks or dollar signs inside `<<'EOF'` heredocs. The single-quoted delimiter already prevents shell expansion, and escaping backticks breaks fence detection, producing garbled output instead of rendered diffs.

Does glimpse-changes support diffs not tied to real files?

Yes. Use `diff` fenced blocks with literal `+`, `-`, and space-prefixed lines for ad-hoc illustrations, or paste full unified diff output including the `diff --git` header.