From beislid
Interactively walks through local git diffs chunk-by-chunk, simulating a colleague explaining changes with context, pausing for questions or flags before advancing.
npx claudepluginhub sandsower/beislidThis skill uses the workspace's default tool permissions.
Simulate sitting next to a colleague who wrote the code and having them walk you through the changes. Present diffs in a logical order with context about why each change was made, highlight decision points and scrutiny areas, then pause so the reviewer can ask questions before moving on.
Generates detailed Markdown walkthroughs of git code changes (uncommitted, staged, commits, branches) with summaries, file tables, explanations, snippets, and testing notes. Saves to tmp dir.
Self-review code changes using GitHub-style visual diff viewer (difit). Add comments on specific lines in browser; comments output to Claude for applying edits via git diff.
Reviews recent git diffs and commits with brutal honesty before PRs, spotting 2am logic flaws, copy-paste artifacts, debug leftovers, hacks, and poor naming.
Share bugs, ideas, or general feedback.
Simulate sitting next to a colleague who wrote the code and having them walk you through the changes. Present diffs in a logical order with context about why each change was made, highlight decision points and scrutiny areas, then pause so the reviewer can ask questions before moving on.
Don't use this for: automated review findings, PR comment posting, fixing feedback, or durable visual reports. Use review, pr-patrol, heard-chef, or explicit show-me instead.
You are the author/presenter, not the reviewer. Explain and defend the change honestly without preemptively rejecting your own code.
The chunk gate is mandatory: never present a new chunk until the reviewer explicitly selects Move on or Flag for follow-up. If the reviewer types free text, treat it as a question/comment, answer it, present the same three options again, and stop.
The three options at every pause are exactly:
Move on — advance to the next chunkI have questions — stay on this chunk; the reviewer will type their question nextFlag for follow-up — note this chunk as needing revisit, then advanceWalk-the-diff phases are authoritative only after their aux files are read. Complete phases in order. At each phase boundary, read the matching file and follow it. If a phase file cannot be read, hard-fail instead of continuing from memory:
🛑 Could not read
skills/walk-the-diff/<phase-file>.md. Walk-the-diff cannot safely execute this phase from memory; reinstall Beislið or restore the file.
skills/walk-the-diff/phase-1-context.mdskills/walk-the-diff/phase-2-tour-plan.mdskills/walk-the-diff/phase-3-present.mdskills/walk-the-diff/phase-4-wrap.mdWhen BEISLID_VERBOSE=1, print one aux load stamp after successfully reading each phase file. Stamp format is ✓ walk-the-diff/<phase-file-stem> v1 loaded for phase-1-context, phase-2-tour-plan, phase-3-present, and phase-4-wrap.
phase-1-context.md. Outputs: base branch/merge base, commits, linked ticket/plans/specs, changed files, surrounding-code notes.phase-2-tour-plan.md. Outputs: ordered chunk list, grouping rationale, reviewer preference if asked.phase-3-present.md. Outputs: each reviewed chunk, questions answered, flags/open items, reviewer gate choices.phase-4-wrap.md only after all chunks are reviewed or flagged. Outputs: overall feedback, saved feedback doc path, final stop.If the user explicitly wants a durable visual walkthrough, proof deck, or local HTML report instead of an interactive chunk-by-chunk review, invoke show-me. Do not run show-me automatically; it is manual/user-requested only in v1.
Move on or Flag for follow-up.