walkthrough

A guide for examining pull request (PR) changes from the point of view of someone using the software.

In plain words
What is it for?
Use it to review a PR by tracing its changes through expected user actions and outcomes.
Why use it?
It helps you judge whether code changes affect real user tasks, not just whether the code looks correct.

Plugin for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add plugins/ryanb/dotfiles/walkthrough
Claude Code
/plugin marketplace add ryanb/dotfiles
Clone the repo
git clone --depth 1 https://github.com/ryanb/dotfiles

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

walkthrough scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

claude/skills/walkthrough/.claude-plugin/plugin.json · 6 lines

What it actually says

{
  "name": "walkthrough",
  "description": "Walk through PR changes from the user's perspective.",
  "skills": "./"
}
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 6 lines scan A 8931d4ae67b9

Subscribe to this mod's changes

walkthrough is a plugin published in the GitHub repository ryanb/dotfiles (2,399 stars, last pushed 12d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.