pr-walkthrough (Warp): a skill that turns a pull request into an interactive map

pr-walkthrough makes your agent build a zoomable web page that maps a pull request, for reviewers who want orientation before reading the diff.

Installs: 28.2K; on skills.sh
Stars: 644; on GitHub
Files: 2; besides SKILL.md
Updated: Oct 2026; last repo commit

The skill reads the current branch's pull request, the diff and the surrounding code. It then writes one self-contained page to .warp/pr-walkthrough/index.html with four separate views: system overview, data flow, code dependencies and user actions. Each view has a guided tour, search and links back to the PR's Files changed tab.

Ask for a PR map, a zoomable PR view or a graph of the pull request. It runs gh and git commands, runs its two bundled Python scripts, and loads the D3 library from a CDN when you open the page. The page uses Warp's brand colors and fonts. SKILL.md says it is an experiment and not a code review: it should not produce review findings.

Good for

Reviewers who open a big PR and need to know where to start
Authors who want to hand reviewers a guided tour of their change
Developers learning an unfamiliar part of a codebase through a PR

Install pr-walkthrough

Claude Code

Copy this prompt.

Install the pr-walkthrough skill in Claude Code. Run this command:

npx skills add https://github.com/warpdotdev/common-skills --skill pr-walkthrough

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

From its listing on skills.sh. Source.

What's in the skill

When it loads

Generate a static interactive D3 walkthrough of a pull request. Use when the user wants a zoomable PR map, graph/canvas PR orientation, or alternate visualization of PR system components, data flow, code dependencies, and user actions.

Sections in SKILL.md

Output
Brand styling
Workflow
1. Establish PR context
2. Collect visual source material
3. Build GitHub diff links
4. Analyze the PR as four guided views
5. Create the canvas data model
6. Build the static site
7. Validate the walkthrough
8. Optional public publishing with Cloudflare Pages
Orientation heuristics
Final response

Key facts

Author: warpdotdev (Warp), repo owner
Repo: warpdotdev/common-skills, path .agents/skills/pr-walkthrough
Installs on skills.sh: 28,207 (as of Nov 2, 2026)
GitHub stars: 644 (shared repo, Nov 2, 2026)
License: MIT (from crawl data)
Last repo commit: Oct 28, 2026
skills.sh audits: Gen Agent Trust Hub: pass. Socket: pass. Snyk: warn.
Files: 3 including SKILL.md: scripts/d3_canvas_runtime.py and scripts/validate_d3_canvas.py
Output: A single HTML file at .warp/pr-walkthrough/index.html, opened from disk

What it includes

Expanded cards that explain the subsystem the PR touches
A short set of component cards that explain the code area without mentioning the PR, changed files or review comments.
System overview view
How state, data and events move through the changed system
Directed graph with arrowheads and labelled edges.
Data flow graph
Which changed parts depend on each other
Shows entry points, leaf dependencies and the main seams.
Code dependency graph
What the user does and how it reaches the code
Starts at the surface the user touches and follows the action through the implementation.
User action graph
Reads the PR, the diff and the git log
Runs `gh pr view`, `git diff`, `git log` and, when a PR exists, `gh api` calls for review comments.
Runs code · Step 1: PR context
Collects screenshots and mocks linked from the PR
Looks in the PR body, comments, changed image files and Figma links. External images are downloaded into the output folder.
Write · Step 2: visual material
Builds Files changed links with a SHA-256 path anchor
Every file reference links to the exact file in the PR diff.
Step 3: diff links
Plans the four views and stores them as JSON in the page
Each view gets nodes, edges and a tour. Sizes scale with the PR: a tiny PR gets 2-3 nodes per view.
Steps 4 and 5: views and data model
Runs scripts/d3_canvas_runtime.py to emit the page
Zoom, pan, search, keyboard shortcuts, tour controls and a detail panel.
Runs code · Step 6: build the site
Runs scripts/validate_d3_canvas.py with --require-browser
Checks the page in a browser through Playwright before the agent calls it ready.
Runs code · Step 7: validate
Deploys the page to Cloudflare Pages with wrangler
Only when you ask for a public URL. Uses `npx wrangler login` and `npx wrangler pages deploy`.
Runs code · Step 8: publish (optional)

From the official docs

Permissions

Medium risk

It runs git, gh and Python scripts in your repo and writes files under .warp/pr-walkthrough. Do not use the optional publish step on private code unless you accept a public URL.

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

Publishing makes your PR context public
Step 8 deploys the page to a public Cloudflare Pages URL when you ask for one. SKILL.md says not to publish private code or sensitive PR context unless you accept that exposure. The step runs `npx wrangler`, which executes the wrangler npm package on your machine. github.com
It runs commands and scripts in your repo
It calls gh, git and two Python scripts, and writes to .warp/pr-walkthrough/. Check the folder is ignored by git, since SKILL.md says to keep it out of version control. github.com
The page loads D3 from a CDN
SKILL.md pins D3 7.9.0 on cdn.jsdelivr.net, so the page needs network access to render. github.com
Browser check needs Playwright
validate_d3_canvas.py imports Playwright and tries bundled Chromium, then system Chrome, then Chromium. SKILL.md says to report rendering as unverified when no browser is available. github.com

Technical details

Talks to	GitHub (gh pr view, gh api). cdn.jsdelivr.net (D3, when the page opens). Cloudflare Pages (publish step only)
Sign-in and keys	Uses your existing gh login. The publish step uses `npx wrangler login`.
Scopes	gh CLI login Cloudflare login (publish step only)

Questions

What does pr-walkthrough do?

It makes your agent build a local web page that explains a pull request through four views: system overview, data flow, code dependencies and user actions. Each view has a guided tour and links to the PR diff.

How do I install it in Claude Code?

Use the install command in the box above. Then ask for a PR walkthrough from a checkout of the branch.

Does it need an API key?

The skill does not ask for one. It uses your gh login to read the PR. The publish step needs a Cloudflare account and npx wrangler login.

Is it safe to run?

It runs gh, git and two bundled Python scripts and writes under .warp/pr-walkthrough/, so read SKILL.md before first use. Only the optional publish step sends the page off your machine, and SKILL.md warns against publishing private code.

Does it review my PR?

No. SKILL.md says it is not a code-review skill and tells the agent not to write new findings or approve/request-changes verdicts. It produces orientation maps from the code, diff, PR text, changed specs and existing comments.

Why is the page Warp-themed?

SKILL.md tells the agent to apply Warp's Brandalf styling: dark surfaces, a pink accent and Matter fonts. It mentions a brandalf skill in the same repo and gives fallback colors if the hosted brand source is unavailable.

Does it only work in Warp's repo or in the Warp terminal?

No. SKILL.md asks for a checkout of the PR branch with gh and git, and does not name Warp's app or repo as a requirement. The Warp parts are the styling (the brandalf skill and Warp colors and fonts), the .warp/pr-walkthrough/ output folder and the example Cloudflare project name warp-pr-walkthroughs. The commands in SKILL.md call the scripts as python3 .agents/skills/pr-walkthrough/scripts/..., the folder used in Warp's repo, so your agent has to run them from wherever the skill was installed.

Do I need the brandalf skill?

It is in the same repo (warpdotdev/common-skills) and SKILL.md tells the agent to use it for the visual design. If the hosted brand source is unavailable, SKILL.md says to continue with its fallback colors and fonts and mention the caveat. It is not required to build the page.

Information

updated Nov 2, 2026

Repository: warpdotdev/common-skills
Folder: .agents/skills/pr-walkthrough

warpdotdev/common-skills skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 1

SKILL.md · github.com