walk-the-diff

Presents local git changes as an interactive, chunk-by-chunk guided walkthrough for human reviewers.

10|Updated May 12, 2026
One-click install
npx skills add https://github.com/sandsower/beislid --skill walk-the-diff-sandsower
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: walk-the-diff
Source: https://github.com/sandsower/beislid/tree/main/skills/walk-the-diff
Command: npx skills add https://github.com/sandsower/beislid --skill walk-the-diff-sandsower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing your own branch before a PR often means dumping a raw diff on a colleague or skimming changes without context. This Skill turns local changes into a structured, interactive walkthrough where the agent acts as the author, explaining each change with intent, decision points, and scrutiny areas. ## Core Features & Use Cases - Context Gathering: Reads merge-base, commit messages, linked tickets, plans, and surrounding code before showing any diff. - Tour Planning: Groups changed files into logical 2-5 minute chunks ordered by narrative, dependency, or user-facing flow. - Gated Presentation: Shows one chunk at a time and only advances on explicit reviewer choices (Move on, I have questions, Flag for follow-up). - Feedback Capture: Saves a structured feedback document with open items and file/line references to user state, outside the repo. - Use Case: Before opening a PR, ask the agent to walk you through your branch; it explains each change like the author sitting next to you, answers questions, and produces a feedback doc you can act on later. ## Quick Start Ask the agent to walk you through the changes on your current branch before opening a pull request.

Frequently Asked Questions about walk-the-diff

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

FAQPage Schema
How do I get a guided walkthrough of my git branch changes?▼

Invoke the walk-the-diff skill on your feature branch. It computes the merge-base against main, reads commit messages and linked tickets, groups changes into logical chunks, and presents each chunk with context while pausing for your input.

What is the difference between walk-the-diff and automated code review?▼

Walk-the-diff is an interactive, human-facing presentation where the agent explains changes as the author and waits for reviewer input. It does not produce automated findings, post PR comments, or fix code; use dedicated review or PR tools for those tasks.

Can walk-the-diff post review comments to a pull request?▼

No. It is explicitly not for PR comment posting or automated review findings. Its only deliverable is a feedback document saved to user state outside the repository after the walkthrough completes.

Where does walk-the-diff save review feedback?▼

Feedback is saved as a Markdown file under ${BEISLID_STATE_DIR:-~/.local/state/beislid}/feedback/, never inside the repository. The file includes chunk statuses, open items with file and line references, and an overall assessment.

What happens if a walk-the-diff phase file is missing?▼

The skill hard-fails with an error message instead of reconstructing the phase from memory. Each of the four phase files must be readable before its phase executes, so you should reinstall or restore the missing file.