New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Glimpse Changes Walkthrough

by cashew-labs in cashew-labs/libretto

Turns the current session's code changes into a Markdown walkthrough shown in a native Glimpse window, with highlighted code, rendered diffs and review feedback.

MITAuto-check passedDevelopment

Install Glimpse Changes Walkthrough

skills CLI
$ npx skills add cashew-labs/libretto --skill glimpse-changes -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cashew-labs/libretto glimpse-changes --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cashew-labs/libretto.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/glimpse-changes .claude/skills/glimpse-changes && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
glimpse-changes
GitHub stars
904
Token cost
~1.5k tokens
SKILL.md length
483 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

Turns the current session's code changes into a Markdown walkthrough shown in a native Glimpse window, with highlighted code, rendered diffs and review feedback.

  • Works in 4 steps: Start with a specific title. → Add a brief summary of what changed. → Choose the walkthrough order that best… → …
  • Getting a visual walkthrough of local code changes before committing
  • SKILL.md covers Setup, How to write a useful…, Usage and User review workflow, plus 3 more sections
  • Calls npx

What it does

Instead of handing you a plain text diff, the agent writes a short Markdown walkthrough of the changes and displays it in a native Glimpse window through the glimpse-changes command, run with npx. The window shows syntax-highlighted code and rendered diffs, using focused changes or diff blocks placed between paragraphs of explanation.

Most of the skill's text is about how to write the walkthrough: a specific title, a brief summary, an order chosen to explain the work rather than to mirror the diff, and prose about intent, tradeoffs and review risks, written the way one developer talks another through a change. Markdown is best piped over stdin with a quoted heredoc, without escaping backticks or dollar signs, and the command blocks until you close the window. Glimpse can also collect your review feedback.

When your agent uses it

  • Getting a visual walkthrough of local code changes before committing
  • Reviewing an agent's session diff in a window instead of raw patch text
  • Explaining a change to another developer in a readable order

Example prompts

  • “Show me what changed in this session as a Glimpse walkthrough.”
  • “Walk me through the diff for the new retry logic in a Glimpse window.”
  • “Open a visual review of my uncommitted changes and let me leave feedback.”

Requirements

  • Node.js with npx to run glimpse-changes
  • A desktop session that can open a native window

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Start with a specific title.
  2. Add a brief summary of what changed.
  3. Choose the walkthrough order that best explains the work.
  4. Use prose between focused changes or diff blocks to explain intent, tradeoffs, and review risks.

What it can do on your machine

Read from SKILL.md and the folder at commit 41ab782. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Glimpse Changes Walkthrough loads about 1.5k tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 483 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~58
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cashew-labs/libretto at commit 41ab782, republished under its MIT licence (© cashew-labs). 483 words, ~1,476 tokens.

Download SKILL.mdSave it as .claude/skills/glimpse-changes/SKILL.md (or your agent's skills folder).
name
glimpse-changes
description
Create a visual explanation of the current session diff as a single HTML page and show it in a native Glimpse window. Use when the user wants a visual walkthrough of local code changes instead of a plain text diff.
metadata.author
tanishqkancharla
metadata.version
1.9.5

Glimpse Changes

Render a Markdown walkthrough in a native Glimpse window with syntax-highlighted code and rich diff rendering.

Setup

bash
npx glimpse-changes@1.9.5 --help

How to write a useful walkthrough

Use Glimpse to walk another developer through the code in the clearest order, not necessarily the order files appear in the diff.

Aim for a short, reviewable document:

  1. Start with a specific title.
  2. Add a brief summary of what changed.
  3. Choose the walkthrough order that best explains the work.
  4. Use prose between focused changes or diff blocks to explain intent, tradeoffs, and review risks.

Prefer a narrative that follows the user or developer flow: what someone sees or does, how the request/state/data moves through the system, then any supporting helpers, tests, docs, or cleanup. If another order is clearer, use that instead.

Write like a developer walking another developer through the change. Be direct and specific. Avoid dumping one large diff with a generic explanation. Prefer smaller, focused sections when they help the reader understand the code.

Good explanation style:

  • "To keep the review focused on selected files, pass the filter through the renderer."
  • "Add a fallback label so empty reviews still have a useful title."
  • "The parser now keeps deleted files in the walkthrough so reviewers can see removals in context."

Template:

md
# <Title>

## Summary

- <User-visible or developer-visible effect>
- <Main code path changed>
- <Important review note, risk, or edge case>

## <First thing a reviewer should understand>

Explain the intent and what to look for.

```changes
path/to/relevant-file.ts:20-70
```

## <Next part of the flow>

Explain how this connects to the previous step.

```changes
path/to/another-file.ts:80-130
```

## <Supporting detail, test, or edge case>

Explain why this support code matters.

```changes
path/to/test-file.test.ts:50-100
```

Example:

bash
cat <<'EOF' | npx glimpse-changes@1.9.5 -
# Improve review flow messaging

## Summary
- make the default review flow easier for agents to follow
- document when to wait for the user versus using background mode
- keep the walkthrough focused on the interaction reviewers care about

## Open the review and wait for the user

To make review sessions easier to follow, tell agents to open Glimpse, ask the
user to inspect it, and wait until the user says they are done.

```changes
packages/glimpse-changes/skills/glimpse-changes/SKILL.md:120-145
```
EOF

Example with an ad-hoc fenced diff block:

bash
cat <<'EOF' | npx glimpse-changes@1.9.5 -
# New utility module

## Summary
- Added a helper for computing hashes

## Hash helper

```diff
+++ src/utils/hash.ts
+import { createHash } from "node:crypto";
+
+export function shortHash(input: string): string {
+  return createHash("sha256")
+    .update("example:" + input)
+    .digest("hex")
+    .slice(0, 12);
+}
```

EOF

Usage

Prefer piping markdown over stdin. This avoids shell-quoting issues.

bash
cat report.md | npx glimpse-changes@1.9.5
cat report.md | npx glimpse-changes@1.9.5 -

cat <<'EOF' | npx glimpse-changes@1.9.5 -
# Title

Content
EOF

Important: Do NOT escape backticks or dollar signs inside <<'EOF' heredocs. The single-quoted delimiter already prevents shell expansion. Escaping backticks will break fence detection and produce garbled output instead of rendered diffs.

You can still pass a single inline markdown argument for simple content:

bash
npx glimpse-changes@1.9.5 "# Title\n\nContent"

The CLI opens a Glimpse window and blocks until closed.

Show full SKILL.md (199 more words)Show less

User review workflow

Glimpse can also collect review feedback from the user.

Default interactive flow:

  1. Render the walkthrough for the user.
  2. Tell the user to review it in Glimpse.
  3. Wait for the user to say they are finished.
  4. Then continue the task.

Use --background only when an asynchronous workflow is useful. In background mode, the CLI prints a review file path. That file contains __PENDING__ until the window is closed, then contains either the user's review text or a no-review completion message.

bash
npx glimpse-changes@1.9.5 --background "# Title\n\nContent"
# prints: Glimpse window opened. Read /tmp/glimpse-review-<id>.txt for user feedback.

Changes blocks

Use changes fenced code blocks to show diffs for real files. List paths relative to the working directory. The renderer resolves old and new contents from git automatically.

Show full file diffs:

md
```changes
src/db/queries.ts
src/db/schema.ts
```

Focus on a line range:

md
```changes
src/config.ts:42-50
```

Use one block for related files, or separate blocks with prose for a guided walkthrough:

md
The query layer now batches reads before returning results:

```changes
src/db/queries.ts:30-95
```

The schema adds the index that makes those batched reads efficient:

```changes
src/db/schema.ts:12-28
```

The renderer handles new files, deleted files, and modified files. If a file cannot be resolved, it shows an error inline.

Inline diffs

For ad-hoc illustrations not tied to real files, use diff fenced blocks with literal +/-/ prefixed lines:

md
```diff
-removed line
+added line
 context line
```

You can also paste full unified diff output:

md
```diff
diff --git a/foo.txt b/foo.txt
--- a/foo.txt
+++ b/foo.txt
@@ -1,3 +1,3 @@
 context
-old
+new
```

Code blocks

Fenced code blocks with a language tag are syntax highlighted:

md
```js
const x = 1;
```

© cashew-labs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/glimpse-changes of cashew-labs/libretto.

Open the folder on GitHubat commit 41ab782

Compare with similar skills

Glimpse Changes Walkthrough next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Glimpse Changes Walkthrough compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Glimpse Changes Walkthrough this skillcashew-labs/libretto904—~1.5kAutomated safety check: PassMIT
PR Walkthroughkdlbs/kandev909—~6.2kAutomated safety check: PassAGPL-3.0
PRP Companion PageWirasm/prp2.3k—~990Automated safety check: PassMIT
@pierre/diffs Code Renderingpierrecomputer/pierre6.2k2 repos~803Automated safety check: PassApache-2.0
Frontend Code Reviewlanggenius/dify158k—~938Automated safety check: PassCustom licence
Archify Diagram BuilderUnclecheng-li/AI_Animation1.5k2 repos~4.1kAutomated safety check: PassMIT

Similar skills

  • PR Walkthrough

    kdlbs/kandev

    Generate a single-file HTML walkthrough that explains a PR's purpose, user impact, interface changes, compatibility risks, and implementation.

    909 GitHub stars~6.2k tokensUpdated today
    DevelopmentAuto-check passed

  • PRP Companion Page

    Wirasm/prp

    Writes a self-contained HTML page beside a PRP plan or review that shows the diagram, steps, risks or findings, with a stable id on every item.

    2.3k GitHub stars~990 tokensUpdated 6 days ago
    DevelopmentAuto-check passed

  • @pierre/diffs Code Rendering

    pierrecomputer/pierre

    Guides an agent through using @pierre/diffs to render syntax-highlighted files and diffs, and to build editing and review surfaces in React or plain JavaScript.

    6.2k GitHub starsUsed in 2 repos~803 tokens
    DevelopmentAuto-check passed

  • Frontend Code Review

    langgenius/dify

    Reviews frontend changes under `web/` or `packages/dify-ui/` for concrete defects and broken project contracts, using routed rule packs and a severity scale for findings.

    158k GitHub stars~938 tokensUpdated today
    DevelopmentAuto-check passed

  • Archify Diagram Builder

    Unclecheng-li/AI_Animation

    Builds validated architecture, workflow, sequence, data-flow and lifecycle diagrams as standalone interactive HTML from a small JSON spec, with optional motion and image export.

    1.5k GitHub starsUsed in 2 repos~4.1k tokens
    DevelopmentAuto-check passed

  • Plannotator Visual Explainer

    backnotprop/plannotator

    Builds self-contained HTML explainers for plans, pull requests and technical concepts in Plannotator's theme, then opens them in its annotation view.

    9.2k GitHub stars~1.7k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from cashew-labs/libretto

All 21 skills in this repo

  • System Prompt Writing Guide

    cashew-labs/libretto

    Lays out a minimal, iteration-first approach to writing system prompts for LLM agents, with model-specific notes for Claude, GPT, Gemini, and Codex.

    904 GitHub stars~570 tokensUpdated 1 mo ago
    Auto-check passed

  • Address PR Review Comments

    cashew-labs/libretto

    Works through the review comments on a pull request one by one: fetches the threads, makes the fixes, runs type-check, build and lint, pushes, and resolves the threads.

    904 GitHub stars~532 tokensUpdated 1 mo ago
    Auto-check passed

  • CLI Development

    cashew-labs/libretto

    Design rules for command-line tools: subcommand-scoped help, actionable success output, debuggable failures, stable output, meaningful exit codes and a --json mode.

    904 GitHub stars~781 tokensUpdated 1 mo ago
    Auto-check passed

  • External Electron App Automation

    cashew-labs/libretto

    Drives desktop Electron apps already installed on your machine, such as Slack, Discord or VS Code, by relaunching them with a debugging port and using the Libretto CLI.

    904 GitHub stars~967 tokensUpdated 1 mo ago
    Auto-check passed

  • Merge Conflict Resolver

    cashew-labs/libretto

    Resolves Git merge, rebase and cherry-pick conflicts by reading the PRs behind each side, keeping both intents and asking you when they truly clash.

    904 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed

  • Feature Spec Generator

    cashew-labs/libretto

    Researches the codebase and relevant docs, asks clarifying questions, then writes a spec sheet in specs/ for a significant feature or complex fix.

    904 GitHub stars~2.4k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Glimpse Changes Walkthrough

What does Glimpse Changes Walkthrough do?

Turns the current session's code changes into a Markdown walkthrough shown in a native Glimpse window, with highlighted code, rendered diffs and review feedback. Instead of handing you a plain text diff, the agent writes a short Markdown walkthrough of the changes and displays it in a native Glimpse window through the glimpse-changes command, run with npx. The window shows syntax-highlighted code and rendered diffs, using focused changes or diff blocks placed between paragraphs of explanation.

When should I use Glimpse Changes Walkthrough?

Glimpse Changes Walkthrough fits situations like: getting a visual walkthrough of local code changes before committing; reviewing an agent's session diff in a window instead of raw patch text; explaining a change to another developer in a readable order.

How do I install Glimpse Changes Walkthrough in Claude Code?

Run `npx skills add cashew-labs/libretto --skill glimpse-changes -a claude-code`. Or copy the skill folder (.agents/skills/glimpse-changes in cashew-labs/libretto) into .claude/skills/glimpse-changes in your project. Claude Code loads it when a task matches its description.

How do I install Glimpse Changes Walkthrough in Codex?

Run `npx skills add cashew-labs/libretto --skill glimpse-changes -a codex`. Or copy the skill folder (.agents/skills/glimpse-changes in cashew-labs/libretto) into .agents/skills/glimpse-changes in your project. Codex loads it when a task matches its description.

Can I use Glimpse Changes Walkthrough in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cashew-labs/libretto --skill glimpse-changes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/glimpse-changes, .gemini/skills/glimpse-changes, .github/skills/glimpse-changes and .opencode/skills/glimpse-changes in your project.

What does Glimpse Changes Walkthrough need to run?

Going by SKILL.md and its folder, Glimpse Changes Walkthrough needs the command-line tools its instructions call (npx). Our summary lists: Node.js with npx to run glimpse-changes; A desktop session that can open a native window.

Does Glimpse Changes Walkthrough access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Glimpse Changes Walkthrough safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Glimpse Changes Walkthrough use?

Glimpse Changes Walkthrough is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Glimpse Changes Walkthrough use?

About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Glimpse Changes Walkthrough?

Skills that share tags, products or a category with Glimpse Changes Walkthrough: PR Walkthrough (kdlbs/kandev, 909 stars), PRP Companion Page (Wirasm/prp, 2.3k stars), @pierre/diffs Code Rendering (pierrecomputer/pierre, 6.2k stars) and Frontend Code Review (langgenius/dify, 158k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Glimpse Changes Walkthrough?

cashew-labs (a GitHub organization) maintains it in cashew-labs/libretto, which has 904 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on August 21, 2026.

Source: cashew-labs/libretto on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.