review-walkthrough — Claude Code skill: step-by-step diff review
Turns the current branch diff into an HTML walkthrough with logical steps, explanations and review findings. Run it by hand when you want to read a change properly.
npx skills add trailofbits/skills --skill review-walkthrough -a claude-codeWhat review-walkthrough does
The skill takes the branch patch and splits it into steps: related files together, definitions before the code that uses them, tests next to their subjects. Commit order does not drive the reading order — the skill picks whatever is easier to follow. Each step gets an explanation of roughly 50–150 words plus a list of findings with severity levels.
Base branch resolution goes in order: the open PR when its metadata is available, otherwise the repository default from git symbolic-ref --quiet --short refs/remotes/origin/HEAD. It will not quietly fall back to main; an ambiguous base means it asks. The patch lands in a temp file outside the checkout, and rendering runs through uv run --no-project {baseDir}/scripts/render_walkthrough.py. So uv has to be on your machine, or the page never gets built.
Review stays read-only. The skill does not run your tests or install dependencies, and it never switches branches. Uncommitted work is excluded from the walkthrough, though it gets mentioned. GitHub metadata only matters for comment export: the page hands you a gh api command to copy, and posts nothing itself.
What it helps with
- split a large diff into readable steps
- explain what each changed file is for
- surface bugs and security issues with severity
- anchor a finding to a line in the diff
- prepare a branch walkthrough before a teammate reviews it
Example prompts for the agent
- /review-walkthrough:review-walkthrough
- $review-walkthrough
- build a walkthrough for this branch against the release branch
How to install review-walkthrough
1Skills CLI (Vercel)
npx skills add trailofbits/skills --skill review-walkthrough -a claude-code2Manually: put the files in place
~/.claude/skills/review-walkthrough/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/review-walkthrough/
1Skills CLI (Vercel)
npx skills add trailofbits/skills --skill review-walkthrough -a codex2Manually: put the files in place
.agents/skills/review-walkthrough/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add trailofbits/skills --skill review-walkthrough -a cursor2Manually: put the files in place
.cursor/skills/review-walkthrough/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install trailofbits/skills review-walkthrough2Manually: put the files in place
.github/skills/review-walkthrough/SKILL.md1Skills CLI (Vercel)
npx skills add trailofbits/skills --skill review-walkthrough -a gemini-cli2Platform CLI
gemini skills install https://github.com/trailofbits/skills --path plugins/review-walkthrough/skills/review-walkthroughManually: put the files in place
.devin/skills/review-walkthrough/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add trailofbits/skills --skill review-walkthrough -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about review-walkthrough
How do I install review-walkthrough in Claude?
Run npx skills add trailofbits/skills --skill review-walkthrough -a claude-code. The skill file then lives at ~/.claude/skills/review-walkthrough/SKILL.md.
What does review-walkthrough do?
It captures the current branch patch, groups it into logical steps with explanations and findings, and renders a self-contained HTML page for review.
How do I invoke it?
In Claude use /review-walkthrough:review-walkthrough; in Claude use $review-walkthrough. It only runs when called explicitly.
